Re: [Call For Testing] VirtualBox for FreeBSD!

[Bernhard Fröhlich]

On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote:
> Few more notes from -CURRENT/amd64
>
> [snip]
>
> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
> ISO results in an error:
>
> Failed to start the virtual machine FreeBSD.
> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}

That is an amd64 problem and it is already being worked on. Sorry no
solution yet.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD!

[Bernhard Fröhlich]

On Thu, May 14, 2009 11:51 pm, Artem Belevich wrote:
> Few more notes from -CURRENT/amd64
>
> [snip]
>
> * Attempt to boot new VM (64-bit FreeBSD) from -current snapshot DVD
> ISO results in an error:
>
> Failed to start the virtual machine FreeBSD.
> Failed to load VMMR0.r0 (VERR_SYMBOL_VALUE_TOO_BIG).
> Unknown error creating VM (VERR_SYMBOL_VALUE_TOO_BIG).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}


I cannot reproduce that anymore (probably hit another problem). Could you
please provide what the vbox-dev people asked for to solve that problem?

VBox.log from ~/.VirtualBox/Machines//Logs/VBox.log

and start with

export VBOX_LOG=+rt_ldr.e.l2.f
VirtualBox -startvm VM_NAME

the resulting .log file (created in the current directory!)

http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001411.html
http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001413.html

Thanks!

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3

[Bernhard Fröhlich]

On Sat, May 23, 2009 2:32 pm, Maho NAKATA wrote:
> Hi miwi,
>
> Here is a patch adding "WITH_GUESTADDITIONS" knob.
> With this knob we also installs
> Guest additions.iso. This driver makes Windows XP, Linux and Solaris
> faster.
> I'm a newbie to VirtualBox so it is not the correct patch.
> I don't check it thoroughly but ISO image itself is not a GPL one.

Thanks, it's commited with a few modifications.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD! take 3

[Bernhard Fröhlich]

On Sun, May 24, 2009 7:04 pm, Ulf Lilleengen wrote:
> On søn, mai 24, 2009 at 07:02:37pm +0200, Ulf Lilleengen wrote:
>> On Fri, May 22, 2009 at 07:59:57PM +0200, Martin Wilke wrote:
>> >
>> > We rolled a new version with a fix for all users where
>> > has problems with kernel load and unload. Many thanks to
>> > Shin-ichi Okano where submitted this patch to the vbox ml.
>> >
>> > http://people.freebsd.org/~miwi/vbox/virtualbox_4.tgz
>> >
>> > happy testing.
>> >
>> >
>> I've had problems with all vbox builds where the machine screen just
>> turns
>> gray:
>> http://people.freebsd.org/~lulf/2009-05-24-185847_1024x768_scrot.png
>>
>> I also have a truss log here (quite big):
>> http://people.freebsd.org/~lulf/virtualbox_truss.log
>>
> I forgot to mention, this is i386, Core Duo CPU

It looks like it's the same problem as a few others already mentioned. You
could try to set kern.hz=1000 which should help. If that's the case please
also test the patch from aeichner that should fix that problem.

http://pastebin.ca/1433127

That patch is from upstream and so young that it's not yet included in the
port but feedback would be great.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD! take 3

[Bernhard Fröhlich]

On Mon, May 25, 2009 8:35 am, Odhiambo  ワシントン wrote:
> On Mon, May 25, 2009 at 9:17 AM, Maho NAKATA  wrote:
>
>> Hi Miwi and nork-san
>>
>> From: Norikatsu Shigemura 
>> Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 3
>> Date: Mon, 25 May 2009 05:17:38 +0900
>>
>> >   BTW, In my environment, VBoxREM32.so and VBoxREM64.so was not
>> >   installed.  Do you know why?
>>
>> I don't know but it also happen to me. I have this problem on
>> 7.2-RELEASE/amd64.
>
> Not to answer but just to say that on my i386, both files were installed.

I've fixed that yesterday so this problem will be gone with the next port
update. Both files only exist on i386 so this problem happens on all amd64
boxes.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFT] GTK frontend for VirtualBox

[Bernhard Fröhlich]

On Tue, June 16, 2009 4:45 pm, Alexander Logvinov wrote:
> Hello!
>
>  For GTK lovers I've created a port for vboxgtk 0.4.1:
> http://www.logvinov.ru/files/dist/vboxgtk.tar . Sometimes it works. :)
>
>  2VBox Team: The latest 0.5.0-beta1 version of vboxgtk wants python
> bindings for the VirtualBox Python API support. Any chance to get it?

Sure. I'll look into it but it can take some days.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD! take 6

[Bernhard Fröhlich]

On Mon, September 7, 2009 7:41 am, Danny Braniss wrote:
>
> [...]
>> > > >
>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is
>> no
>> > > longer available, there is a
>> > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2
>> > > then again in ports/emulatores/virtualbox the version is
>> 3.0.51r6,
>> > >
>> > > can someone please explain?
>
> hi, the above was my question, which was totally ignored, not nice.
> I will try and refrase it:
> the call for testing is for a version (2.2.51r20457) which is not
> available, while
> the ports is 3.0.51r6, so while I managed to compile it, it complains
> that COM
> is not running, all this under 8BETA-3, both under 32 and 64 bit.

I'll try to be nice but it is still unclear to me what you want. The file
is available on all 4 master sites that are listed in the ports Makefile.

The virtualbox port is still in heavy development so it is strongly
recommended that you use the latest version that is in the ports. If that
also does not work you could give our svn version a try but be careful
with it because it can break in strange ways or destroy your virtual
machines.

svn co
http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call For Testing] VirtualBox for FreeBSD! take 6

[Bernhard Fröhlich]

On Mon, September 7, 2009 7:48 pm, Olivier Smedts wrote:
> 2009/9/7 Bernhard Fröhlich :
>> On Mon, September 7, 2009 7:41 am, Danny Braniss wrote:
>>>
>>> [...]
>>>> > > >
>>>> > > ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is
>>>> no
>>>> > > longer available, there is a
>>>> > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2
>>>> > > then again in ports/emulatores/virtualbox the version is
>>>> 3.0.51r6,
>>>> > >
>>>> > > can someone please explain?
>>>
>>> hi, the above was my question, which was totally ignored, not nice.
>>> I will try and refrase it:
>>> the call for testing is for a version (2.2.51r20457) which is not
>>> available, while
>>> the ports is 3.0.51r6, so while I managed to compile it, it
>>> complains
>>> that COM
>>> is not running, all this under 8BETA-3, both under 32 and 64 bit.
>>
>> I'll try to be nice but it is still unclear to me what you want. The
>> file
>> is available on all 4 master sites that are listed in the ports
>> Makefile.
>>
>> The virtualbox port is still in heavy development so it is strongly
>> recommended that you use the latest version that is in the ports. If
>> that
>> also does not work you could give our svn version a try but be careful
>> with it because it can break in strange ways or destroy your virtual
>> machines.
>>
>> svn co
>> http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox/
>
> Wow... the SVN version works great for me with VT extensions ! I just
> tried a 64 bits 2 processors guest :)
>
> Thanks !

According to Alexander Eichner VT-x should work now with the latest vbox
code. So everybody who is using our svn port should already have working
VT-x. We plan to update the virtualbox port in the next few days to get
that version in the tree before the ports freeze.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox-kmod fails to build on -CURRENT

[Bernhard Fröhlich]

On Di.,   1. Nov. 2011 18:33:54 CET, Ed Schouten  wrote:

> * Marco Steinbach , 2001 18:18:
> > You were right about the device naming, I had to create a symlink.
> 
> Okay. I've attached a new version of the patch that:
> 
> - Adds a symbolic link from /dev/vboxdrv0 to /dev/vboxdrv automatically,
> - Changes the code to use /dev/vboxdrv.
> 
> This means the kernel module is backwards compatible, but VirtualBox
> itself isn't. This is probably a good compromise.
> 
> I trust that the warnings and traces you are seeing are in no way
> related to my patch, so I suppose you're better off reporting those to
> the VirtualBox developers.
> 
> decke@, (or who else maintains VirtualBox), will you do the honour of
> getting the patch upstreamed/applied locally? The patch probably has to
> be used by both the virtualbox-ose and the virtualbox-ose-kmod port.
> Thanks!

Thanks a lot for the patch. To be able to submit it upstream please reply if it 
is okay that the patch is licensed under the MIT License so that Oracle can 
include it in their products.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose-kmod fails on HEAD

[Bernhard Fröhlich]

On Sa., 12. Nov. 2011 08:55:31 CET, Doug Barton  wrote:

> I'm running r227447 and get the following:
> 
> cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX
> -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS
> -DRT_ARCH_AMD64 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
> -nostdinc   -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq
> -finline-limit=8000 --param inline-unit-growth=100 --param
> large-function-growth=1000 -fno-common   -fno-omit-frame-pointer
> -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float
> -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
> -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes   -Wmissing-prototypes
> -Wpointer-arith -Winline -Wcast-qual   -Wundef -Wno-pointer-sign
> -fformat-extensions   -Wmissing-include-dirs -fdiagnostics-show-option -c
> /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c
> /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c:104:
> error: 'D_PSEUDO' undeclared here (not in a function)
> *** Error code 1
> 
> Stop in
> /usr/local/tmp/frontier/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/debug/bin/src/vboxdrv.
> *** Error code 1

look for the patch in ports/162186
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org - The public FreeBSD ports development infrastructure

[Bernhard Fröhlich]

On Do., 29. Dez. 2011 15:26:12 CET, Vitaly Magerya  wrote:

> Bernhard Froehlich wrote:
> > Hi Porters!
> > 
> > I am happy to announce that redports.org has finally
> > reached the point where I think It's safe to be used
> > by everybody!
> 
> First of all, this is pretty great.
> 
> Next, questions, comments & feature requests.
> 
> 1. It would be good to see what is currently in the queue for each
> backend (or buildgroup) right now; just to get an estimation of when
> your build will finish (e.g. "in a few minutes" vs. "in a month"). An
> actual estimation would be even better.

Showing the buildqueue is easy but making predictions from the list is nearly 
impossible. There is a scheduling algorithm that tries to be fair but it cannot 
do much more than that. 

> 2. GCC 4.5 buildgroup currently shows 0 queued builds, but for some
> reason my build in that buildgroup does not start. Is there really
> nothing queued there?

Currently all builds are on the same machine and there is a limit of 2 parallel 
builds for this machine.

> 3. On "My builds" page I see two strange builds in "waiting" state: one
> for buildgroup "GCC" another for "4.5"; should that be one buidgroup
> "GCC 4.5"?

Sounds like a bug. I will have a look at that.

> 4. Is each backend a separate physical (or virtual) machine (i.e. do
> they all operate independently)? Are more machines planned?

There is currently only one backend machine that is limited to two parallel 
builds. It is a 6 core Phenom II with 16GB Ram so performance is quite decent 
but more hardware will be needed over time. I would also like to get get some 
Tier-2 hardware like powerpc or sparc if there is enough interest. So 
organizing more hardware is on my todo but it will take some time.

> 5. Is there a way to see all the build archive, not just yours when you
> are logged in?

No currently not but this is only a cosmetic thing and easy to fix. I've put it 
on my todo.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org - The public FreeBSD ports development infrastructure

[Bernhard Fröhlich]

On Do., 29. Dez. 2011 19:13:46 CET, Stephen Montgomery-Smith 
 wrote:

> I am trying this out.   Looking at the instructions on 
> https://redports.org/wiki/UserGuide:
> 
> 
> svn co https://svn.redports.org/
> mkdir www
> cp -pr /usr/ports/www/phpvirtualbox www/
> svn add www
> svn commit -m "phpvirtualbox added"
> 
> shouldn't there be a second line "cd " or something like
> that?

Yes, thanks for spotting that! It's fixed now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org - The public FreeBSD ports development infrastructure

[Bernhard Fröhlich]

On Do., 29. Dez. 2011 17:55:06 CET, Marin Atanasov Nikolov  
wrote:

> On Thu, Dec 29, 2011 at 6:08 PM, Frank Laszlo 
> wrote:
> > On 12/29/11 6:44 AM, Bernhard Froehlich wrote:
> > > 
> > > Hi Porters!
> > > 
> > > I am happy to announce that redports.org has finally
> > > reached the point where I think It's safe to be used
> > > by everybody!
> > 
> > 
> > FYI, I'm getting a 502 bad gateway error when loading the page.
> > 
> 
> Me too :(
> 
> BTW, has anyone considered evaluating Jenkins [1] for doing the same
> thing?
> 
> Jenkins is quite interesting IMO, and is worth testing it out :)
> 
> [1] http://jenkins-ci.org/
> 
> Regards,
> Marin

I spend a few months planning and researching how to best implement the idea in 
a way that fits into the FreeBSD ecosystem. Throwing that all away and using a 
java based finished product will take a lot more time to only reimplement the 
status quo.

Redports has been designed with care to heavily use Tinderbox and ZFS for 
actual building and only reimplement what is really needed. The result is 
easily extendable and written in C, shell and python for the Trac plugin.

http://svn.bluelife.at/index.cgi/redports/browse/trunk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org - The public FreeBSD ports development infrastructure

[Bernhard Fröhlich]

On Sa., 31. Dez. 2011 23:26:14 CET, Vitaly Magerya  wrote:

> Bernhard, is there a time limit on build execution, or some other kind
> of hang prevention?

Yes, there is some limit in tinderbox but I think it's somewhere around 24 
hours.

> My port (lang/stklos) has a known problem with hanging on 9.x, and
> it's already been building for 90 minutes (normally it takes one)...
> So, if you'll read this message before it is finished, please just
> kill it.
> 
> This brings me to a feature request: being able to abort your own
> builds before they are finished.

This should be possible so I've added it to the todo list for the upcoming 
versions.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for Testers: VirtualBox 4.0.4

[Bernhard Fröhlich]

- Ursprüngliche Mitteilung -
> On Fri, 2011-02-18 at 15:21 +0100, Bernhard Froehlich wrote:
> > Hi Testers.
> > 
> > A few of you have probably wondered what happened to our VirtualBox
> > efforts for FreeBSD. Well it took a bit longer then expected and a few
> > problems were found that needed to be resolved first but most of the
> > things are looking fine now and almost all patches have been pushed
> > upstream with 4.0.4 so here we are now.
> > 
> > We will continue to work on VirtualBox for FreeBSD and upstream is also
> > very helpful to us but we could need a few more hands to better keep up
> > with the work and especially improve and fix the Guest Additions. So if
> > you want to help please contact us or have a look at our Todo list.
> > 
> > This result wouldn't have been possible without the continuous help of
> > the VirtualBox Developers and a lot of people from the FreeBSD
> > community! (names in alphabetical order and probably missed a few,
> > sorry
> > for that!)
> > 
> > - Alexander Eichner
> > - Anonymous
> > - Beat Gätzi
> > - Bernhard Fröhlich
> > - crsd
> > - DomiX
> > - Doug Barton
> > - Grzegorz Blach
> > - Hans Petter Selasky
> > - Julian Stacey
> > - Jung-uk Kim
> > - Jürgen Lock
> > - Klaus Espenlaub
> > - Martin Wilke
> > - Mattia Rossi
> > - Michael Butler
> > - Sean C. Farley
> > - Steve Wills
> > - tombsd
> > - Vivek Khera
> > - well-wisher
> > - Wietse Venema
> > - Yuri
> > - many more from emulation@
> > 
> > Please when testing this ports backup all your virtual machines first.
> > Also please build the port with DEBUG option enabled and send us the
> > logfile when any VM crashes. Without them it's very hard to figure out
> > what went wrong.
> > 
> > 
> > Highlights with 4.0:
> > - USB support (by Hans Petter Selasky)
> > - Asynchronous I/O
> > - Guest additions got startscripts and a integration into the desktop
> > environments
> > - www/phpvirtualbox updated to 4.0-3
> > 
> > Changelog for 4.0:
> > - http://www.virtualbox.org/wiki/Changelog
> > 
> > Short configuration help:
> > - http://wiki.freebsd.org/VirtualBox
> > 
> > Todo List:
> > - http://wiki.freebsd.org/VirtualBox/ToDo
> > 
> > 
> > http://home.bluelife.at/ports/virtualbox-cft-20110218.tar.gz
> > 
> > 
> > Thanks and good luck,
> > Bernhard, on behalf of the FreeBSD Vbox Team
> > 
> 
> Hi Folks
> 
> Seems to be working ok for me...
> I had to;
> * remove stale /usr/ports/emulators/virualbox* directories (old patch
> file was causing build to fail)

I should have mentioned that. Please move the old ports out of the way first.

> * remove the stale vboxusers group, the install was complaining cause it
> couldn't set vboxusers gid to 920

Sounds strange and should not happen.
 
> # uname -rp
> 8.1-RELEASE-p2 i386
> 
> I have tried fedora and windows xp guests, both running fine.
> 
> I cant seem to get usb pass through working tho, when I go to add usb
> device it says 'no devices available', do we need to manually setup the
> device info ?

Yeah i want to document it on the virtualbox wiki page but until that you could 
search for the mail of hans petter selasky on the vbox-dev mailinglist.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for Testers: VirtualBox 4.0.4

[Bernhard Fröhlich]

- Ursprüngliche Mitteilung -
> On 02/18/11 11:58, Sergey V. Dyatko wrote:
> > On Fri, 18 Feb 2011 15:21:52 +0100
> > Bernhard Froehlich   wrote:
> > 
> > > Hi Testers.
> > > 
> > > A few of you have probably wondered what happened to our VirtualBox
> > > efforts for FreeBSD. Well it took a bit longer then expected and a
> > > few problems were found that needed to be resolved first but most of
> > > the things are looking fine now and almost all patches have been
> > > pushed upstream with 4.0.4 so here we are now.
> > > 
> > > We will continue to work on VirtualBox for FreeBSD and upstream is
> > > also very helpful to us but we could need a few more hands to better
> > > keep up with the work and especially improve and fix the Guest
> > > Additions. So if you want to help please contact us or have a look at
> > > our Todo list.
> > > 
> > > This result wouldn't have been possible without the continuous help
> > > of the VirtualBox Developers and a lot of people from the FreeBSD
> > > community! (names in alphabetical order and probably missed a few,
> > > sorry
> > > for that!)
> > > 
> > > - Alexander Eichner
> > > - Anonymous
> > > - Beat Gätzi
> > > - Bernhard Fröhlich
> > > - crsd
> > > - DomiX
> > > - Doug Barton
> > > - Grzegorz Blach
> > > - Hans Petter Selasky
> > > - Julian Stacey
> > > - Jung-uk Kim
> > > - Jürgen Lock
> > > - Klaus Espenlaub
> > > - Martin Wilke
> > > - Mattia Rossi
> > > - Michael Butler
> > > - Sean C. Farley
> > > - Steve Wills
> > > - tombsd
> > > - Vivek Khera
> > > - well-wisher
> > > - Wietse Venema
> > > - Yuri
> > > - many more from emulation@
> > > 
> > > Please when testing this ports backup all your virtual machines
> > > first. Also please build the port with DEBUG option enabled and send
> > > us the logfile when any VM crashes. Without them it's very hard to
> > > figure out what went wrong.
> > > 
> > > 
> > > Highlights with 4.0:
> > > - USB support (by Hans Petter Selasky)
> > > - Asynchronous I/O
> > > - Guest additions got startscripts and a integration into the desktop
> > > environments
> > > - www/phpvirtualbox updated to 4.0-3
> > > 
> > > Changelog for 4.0:
> > > - http://www.virtualbox.org/wiki/Changelog
> > > 
> > > Short configuration help:
> > > - http://wiki.freebsd.org/VirtualBox
> > > 
> > > Todo List:
> > > - http://wiki.freebsd.org/VirtualBox/ToDo
> > > 
> > > 
> > > http://home.bluelife.at/ports/virtualbox-cft-20110218.tar.gz
> > > 
> > > 
> > > Thanks and good luck,
> > > 
> 
> In my dmesg:
> 
> KLD vboxdrv.ko: depends on kernel - not available or version mismatch
> linker_load_file: Unsupported file type
> KLD vboxdrv.ko: depends on kernel - not available or version mismatch
> linker_load_file: Unsupported file type
> KLD vboxnetflt.ko: depends on vboxdrv - not available or version mismatch
> linker_load_file: Unsupported file type
> 
> beta# uname -a
> FreeBSD beta.maestro.njit.edu 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Tue 
> Dec 14 18:24:33 EST 2010         
> tkell...@beta.maestro.njit.edu:/usr/obj/usr/src/sys/NOVNINE   amd64
> 
> Rebuilding world and kernel, now, just to be sure I'm following the 
> directions:   I csup /usr/src and /usr/ports hourly

yeah that's a bad idea. The kernel sources and the kernel need to be in sync 
when compiling the vbox kernel module.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Redmine update

[Bernhard Fröhlich]

On So., 20. Mai. 2012 16:02:04 CEST, Mikhail Tsatsenko  
wrote:

> 2012/5/19 Nicolas Raspail :
> > Hello
> > 
> > I see that there is a pr (ports/166087) to update Redmine from 1.3.1 to
> > 1.3.2 that have been updated on Sat May 5 2012.
> > 
> > Now, there is two stable Redmine versions, 1.4.2 and 2.0.0, that are
> > compatible with ruby 1.9 and Rubygem 1.8.
> > 
> > Is someone working on updating this ports ?
> Hi,
> I have a patch to update redmine to 2.0, but it requires a newer rails
> version (3.2.3) than ports tree has (there is 3.2.1 in the ports
> tree). So it can not be commited until rails gets an update. It is
> better to ask ruby@ team about rails update I think.

Why do you think this is worth it? The port is in the current shape because 
upstream is unable to do proper software development and make redmine work with 
different versions of its dependencies. So what will happen when we have ruby 
3.2.3? It will work until we have ruby 3.2.4 or what?

If you really want to improve the situation have a look at ChiliProject because 
they actually care about that. So better create a port for that.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Unable to update to virtualbox-ose-additions 4.1.16

[Bernhard Fröhlich]

On Do.,   7. Jun. 2012 12:33:38 CEST, Alexandre  wrote:

> Hi,
> 
> I am running a VM VirtualBox with FreeBSD 9-STABLE (updated on 06/05/12),
> initially with VirtualBox 4.1.8.
> Now I want to update my ports, but I can't update
> . My ports tree is up-to-date.
> I use the command <# portmaster -a -D --no-confirm> to update ports with
> portmaster tool.
> 
> The error is :
> [...]
> The failing command:
> @cc                                   -m64     -o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/main.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-host.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/thread.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o
>     -L/usr/X11R6/lib32   -L/usr/X11R6/lib   -L/usr/lib   -L/usr/X11R6/lib
>   -L/usr/local/lib     -liconv
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a
> 
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a
> 
> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a
>     -lX11     -lXrandr     -lXt     -lsupc++     -lgcc_eh     -lXext     -lXmu
> -lpthread     -liconv
> *** Error code 2
> 
> Stop in /usr/ports/emulators/virtualbox-ose-additions.
> *** Error code 1
> 
> Stop in /usr/ports/emulators/virtualbox-ose-additions.
> 
> ===>>> make failed for emulators/virtualbox-ose-additions
> ===>>> Aborting update
> 
> ===>>> Update for emulators/virtualbox-ose-additions failed
> ===>>> Aborting update
> 
> Terminated
> [...]
> 
> I posted the full output (with "script") here :
> http://pastebin.com/cmBbqzKx
> 
> --
> 
> Info of the FreeBSD VM guest:
> 
> # uname -a
> FreeBSD VirtualBox 9.0-STABLE FreeBSD 9.0-STABLE #0: Tue Jun   5 16:03:26
> CEST 2012         root@VirtualBox:/usr/obj/usr/src/sys/GENERIC   amd64
> 
> # pkg_info | grep virtualbox
> virtualbox-ose-additions-4.1.8 VirtualBox additions for FreeBSD guests
> 
> --
> 
> This VM is installed on a Windows 7 host (VirtualBox 4.1.16r78094).
> 
> Thanks for your help.

This is a bug in libsupc++ that was merged to 9-STABLE some time ago. You can 
apply the following patch to /usr/src (and reinstall world) or wait around one 
week until the fix will be MFCd.

http://home.bluelife.at/patches/libsupcpp-fix-new-operator-9-STABLE.diff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [new-port] JDownloader

[Bernhard Fröhlich]

On So.,   1. Jul. 2012 19:32:58 CEST, Fernando Apesteguía 
 wrote:

> Hi all,
> 
> I have a preliminary version of a port for JDownloader[1] since it
> seems to be a wanted port[2]
> 
> Here is the Makefile:
> 
> ---
> # New ports collection makefile for:    jdownloader
> # Date created:                                       Sun Jul 1 2012
> # Whom:                    Fernando Apesteguia 
> #
> # $FreeBSD$
> 
> PORTNAME=    jdownloader
> PORTVERSION=    1.0
> CATEGORIES=    java ftp
> MASTER_SITES=    http://212.117.163.148/
> DISTNAME=    jd.sh
> EXTRACT_SUFX=
> 
> MAINTAINER=    fernando.apesteg...@gmail.com
> COMMENT=    Download management for one-click-hosters
> 
> RUN_DEPENDS=    ${LOCALBASE}/bin/java:${PORTSDIR}/java/diablo-jdk16
> RUN_DEPENDS+=    ${LOCALBASE}/bin/wget:${PORTSDIR}/ftp/wget
> 
> USE_JAVA=    yes
> JAVA_VERSION=    1.6+
> NO_BUILD=    yes
> 
> WRKSRC=        ${WRKDIR}
> 
> do-extract:
>     @${MKDIR} ${WRKDIR}
>     @${CP} ${DISTDIR}/jd.sh ${WRKSRC}
> 
> do-install:
>     @${MKDIR} ${PREFIX}/${PORTNAME}
>     @${INSTALL_SCRIPT} ${WRKSRC}/jd.sh ${PREFIX}/bin
> 
> post-install:
>     @${ECHO_MSG} ""
>     @${ECHO_MSG}
> "*"
>     @${ECHO_MSG} JDownloader will update itself to the latest version when
> it runs for the    @${ECHO_MSG} first time. Please run
> ${LOCALBASE}/bin/jd.sh    @${ECHO_MSG} to complete the installation
>     @${ECHO_MSG}
> "*"
>     @${ECHO_MSG} ""    @${CAT} ${PKGMESSAGE}
> 
> .include 
> ---
> 
> The port just needs a simple patch file (patch-jd.sh):
> 
> ---
> --- jd.sh.orig    2012-07-01 14:23:07.0 +0200
> +++ jd.sh    2012-07-01 14:24:15.0 +0200
> @@ -1,4 +1,4 @@
> -#!/bin/bash
> +#!/bin/sh
>   #JD Installer/Starter Version 0.2
>   #by Jiaz(JD-Team), j...@jdownloader.org
>   #You need at least:
> ---
> 
> The jd.sh runs fine with sh(1) so there is no need for a new run
> dependency for bash(1).
> 
> The port installs one single file (jd.sh). This script when executed,
> checks for the presence of the JDownloader jar files under the ~/.jd
> directory. If they don't exist it starts the uploader application and
> downloads the latest files. If the files were already present, it
> launches the installation and if the installation is already present,
> it launches the program.
> Uninstalling the port uninstalls the jd.sh file but _not_ the actual
> application that might be installed by the users in their respective
> home directories. Taking into account that JDownloader can be
> installed anyway just by downloading the source I don't suppose this
> is a concern. Since the program can act as a server (it installs a
> plugin for remote controlling the application similarly to what
> transmission torrent does), it shows a message after the installation.
> 
> I haven't submitted a PR yet, so any suggestions are welcomed.
> 
> Thanks in advance.
> 
> [1] http://jdownloader.org/
> [2] http://wiki.freebsd.org/WantedPorts

Is there a reason why you explicitly add diablo-jdk16 as runtime dependency? 
The use_java stuff should be sufficient.

Why have you decided to download and install the jar files on first run of the 
shellscript? That doesn't sound like a good idea to me because it breaks proper 
updates, deinstall and creates useless binary packages.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [new-port] JDownloader

[Bernhard Fröhlich]

On So.,   1. Jul. 2012 20:09:09 CEST, Fernando Apesteguía 
 wrote:

> On Sun, Jul 1, 2012 at 7:44 PM, Bernhard Fröhlich 
> wrote:
> > On So.,     1. Jul. 2012 19:32:58 CEST, Fernando Apesteguía
> >  wrote:
> > 
> > > Hi all,
> > > 
> > > I have a preliminary version of a port for JDownloader[1] since it
> > > seems to be a wanted port[2]
> > > 
> > > Here is the Makefile:
> > > 
> > > ---
> > > # New ports collection makefile for:       jdownloader
> > > # Date created:                                                           
> > >                   Sun Jul 1 2012
> > > # Whom:                                       Fernando Apesteguia
> > >  #
> > > # $FreeBSD$
> > > 
> > > PORTNAME=       jdownloader
> > > PORTVERSION=       1.0
> > > CATEGORIES=       java ftp
> > > MASTER_SITES=       http://212.117.163.148/
> > > DISTNAME=       jd.sh
> > > EXTRACT_SUFX=
> > > 
> > > MAINTAINER=       fernando.apesteg...@gmail.com
> > > COMMENT=       Download management for one-click-hosters
> > > 
> > > RUN_DEPENDS=       ${LOCALBASE}/bin/java:${PORTSDIR}/java/diablo-jdk16
> > > RUN_DEPENDS+=       ${LOCALBASE}/bin/wget:${PORTSDIR}/ftp/wget
> > > 
> > > USE_JAVA=       yes
> > > JAVA_VERSION=       1.6+
> > > NO_BUILD=       yes
> > > 
> > > WRKSRC=               ${WRKDIR}
> > > 
> > > do-extract:
> > > @${MKDIR} ${WRKDIR}
> > > @${CP} ${DISTDIR}/jd.sh ${WRKSRC}
> > > 
> > > do-install:
> > > @${MKDIR} ${PREFIX}/${PORTNAME}
> > > @${INSTALL_SCRIPT} ${WRKSRC}/jd.sh ${PREFIX}/bin
> > > 
> > > post-install:
> > > @${ECHO_MSG} ""
> > > @${ECHO_MSG}
> > > "*"
> > > @${ECHO_MSG} JDownloader will update itself to the latest version
> > > when it runs for the       @${ECHO_MSG} first time. Please run
> > > ${LOCALBASE}/bin/jd.sh       @${ECHO_MSG} to complete the installation
> > > @${ECHO_MSG}
> > > "*"
> > > @${ECHO_MSG} ""       @${CAT} ${PKGMESSAGE}
> > > 
> > > .include 
> > > ---
> > > 
> > > The port just needs a simple patch file (patch-jd.sh):
> > > 
> > > ---
> > > --- jd.sh.orig       2012-07-01 14:23:07.0 +0200
> > > +++ jd.sh       2012-07-01 14:24:15.0 +0200
> > > @@ -1,4 +1,4 @@
> > > -#!/bin/bash
> > > +#!/bin/sh
> > > #JD Installer/Starter Version 0.2
> > > #by Jiaz(JD-Team), j...@jdownloader.org
> > > #You need at least:
> > > ---
> > > 
> > > The jd.sh runs fine with sh(1) so there is no need for a new run
> > > dependency for bash(1).
> > > 
> > > The port installs one single file (jd.sh). This script when executed,
> > > checks for the presence of the JDownloader jar files under the ~/.jd
> > > directory. If they don't exist it starts the uploader application and
> > > downloads the latest files. If the files were already present, it
> > > launches the installation and if the installation is already present,
> > > it launches the program.
> > > Uninstalling the port uninstalls the jd.sh file but _not_ the actual
> > > application that might be installed by the users in their respective
> > > home directories. Taking into account that JDownloader can be
> > > installed anyway just by downloading the source I don't suppose this
> > > is a concern. Since the program can act as a server (it installs a
> > > plugin for remote controlling the application similarly to what
> > > transmission torrent does), it shows a message after the
> > > installation.
> > > 
> > > I haven't submitted a PR yet, so any suggestions are welcomed.
> > > 
> > > Thanks in advance.
> > > 
> > > [1] http://jdownloader.org/
> > > [2] http://wiki.freebsd.org/WantedPorts
> > 
> > Is there a reason why you explicitly add diablo-jdk16 as runtime
> > dependency? The use_java stuff should be suff

Re: [new-port] JDownloader

[Bernhard Fröhlich]

On Sun, Jul 1, 2012 at 11:49 PM, Fernando Apesteguía
 wrote:
>
> El 01/07/2012 20:45, "Bernhard Fröhlich"  escribió:
>>
>> On So.,   1. Jul. 2012 20:09:09 CEST, Fernando Apesteguía
>>  wrote:
>>
>> > On Sun, Jul 1, 2012 at 7:44 PM, Bernhard Fröhlich 
>> > wrote:
>> > > On So., 1. Jul. 2012 19:32:58 CEST, Fernando Apesteguía
>> > >  wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > I have a preliminary version of a port for JDownloader[1] since it
>> > > > seems to be a wanted port[2]
>> > > >
>> > > > Here is the Makefile:
>> > > >
>> > > >
>> > > > ---
>> > > > # New ports collection makefile for:   jdownloader
>> > > > # Date created:
>> > > > Sun Jul 1 2012
>> > > > # Whom:   Fernando Apesteguia
>> > > >  #
>> > > > # $FreeBSD$
>> > > >
>> > > > PORTNAME=   jdownloader
>> > > > PORTVERSION=   1.0
>> > > > CATEGORIES=   java ftp
>> > > > MASTER_SITES=   http://212.117.163.148/
>> > > > DISTNAME=   jd.sh
>> > > > EXTRACT_SUFX=
>> > > >
>> > > > MAINTAINER=   fernando.apesteg...@gmail.com
>> > > > COMMENT=   Download management for one-click-hosters
>> > > >
>> > > > RUN_DEPENDS=
>> > > > ${LOCALBASE}/bin/java:${PORTSDIR}/java/diablo-jdk16
>> > > > RUN_DEPENDS+=   ${LOCALBASE}/bin/wget:${PORTSDIR}/ftp/wget
>> > > >
>> > > > USE_JAVA=   yes
>> > > > JAVA_VERSION=   1.6+
>> > > > NO_BUILD=   yes
>> > > >
>> > > > WRKSRC=   ${WRKDIR}
>> > > >
>> > > > do-extract:
>> > > > @${MKDIR} ${WRKDIR}
>> > > > @${CP} ${DISTDIR}/jd.sh ${WRKSRC}
>> > > >
>> > > > do-install:
>> > > > @${MKDIR} ${PREFIX}/${PORTNAME}
>> > > > @${INSTALL_SCRIPT} ${WRKSRC}/jd.sh ${PREFIX}/bin
>> > > >
>> > > > post-install:
>> > > > @${ECHO_MSG} ""
>> > > > @${ECHO_MSG}
>> > > >
>> > > > "*"
>> > > > @${ECHO_MSG} JDownloader will update itself to the latest version
>> > > > when it runs for the   @${ECHO_MSG} first time. Please run
>> > > > ${LOCALBASE}/bin/jd.sh   @${ECHO_MSG} to complete the
>> > > > installation
>> > > > @${ECHO_MSG}
>> > > >
>> > > > "*"
>> > > > @${ECHO_MSG} ""   @${CAT} ${PKGMESSAGE}
>> > > >
>> > > > .include 
>> > > >
>> > > > ---
>> > > >
>> > > > The port just needs a simple patch file (patch-jd.sh):
>> > > >
>> > > >
>> > > > ---
>> > > > --- jd.sh.orig   2012-07-01 14:23:07.0 +0200
>> > > > +++ jd.sh   2012-07-01 14:24:15.0 +0200
>> > > > @@ -1,4 +1,4 @@
>> > > > -#!/bin/bash
>> > > > +#!/bin/sh
>> > > > #JD Installer/Starter Version 0.2
>> > > > #by Jiaz(JD-Team), j...@jdownloader.org
>> > > > #You need at least:
>> > > >
>> > > > ---
>> > > >
>> > > > The jd.sh runs fine with sh(1) so there is no need for a new run
>> > > > dependency for bash(1).
>> > > >
>> > > > The port installs one single file (jd.sh). This script when
>> > > > executed,
>> > > > checks for the presence of the JDownloader jar files under the ~/.jd
>> > > > directory. If they don't exist it starts the uploader application
>> > > > and
>> > > > downloads the latest files. If the files were already present, it
>> > > > launches the installation and if the installation is already
>&g

Re: Jenkins+FreeBSD handbooks

[Bernhard Fröhlich]

On Fri, Aug 3, 2012 at 8:54 PM, Marin Atanasov Nikolov  wrote:
> Hello,
>
> Sometime ago I have been asked by a few fellow FreeBSD users for a
> Jenkins+FreeBSD handbooks.
>
> It took me some time in order to get them published, but here they
> are. Hope you find them useful.
>
> * Continuous Integration with Jenkins under FreeBSD [1]
> * Building project's documentation with Jenkins and Doxygen [2]
> * Code analysis with Jenkins and Clang scan-build [3]
> * Continuous package building with poudriere and Jenkins under FreeBSD [4]
>
> A Jenkins CI instance with the above documentations and projects can
> be found in [5].
>
> Regards,
> Marin
>
> [1]: http://unix-heaven.org/jenkins-continuous-integration-under-freebsd
> [2]: http://unix-heaven.org/building-documentation-with-jenkins
> [3]: http://unix-heaven.org/code-analysis-with-jenkins-and-scan-build
> [4]: 
> http://unix-heaven.org/continuous-package-building-with-poudriere-and-jenkins
> [5]: http://jenkins.unix-heaven.org/jenkins/

Thanks a lot for that tutorials. They look very interesting and I was
always curious how much work it would have been to implement something
like redports.org on top of Jenkins. But obviously my decision was
correct that jenkins would not fit in such a situation.

A more suitable place for jenkins would be automatic building our doc
tree on every commit. But I don't know if that doesn't already exist.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Jenkins+FreeBSD handbooks

[Bernhard Fröhlich]

On Fri, Aug 3, 2012 at 9:33 PM, Marin Atanasov Nikolov  wrote:
> On Fri, Aug 3, 2012 at 10:14 PM, Bernhard Fröhlich  wrote:
>>
>
> Hello Bernhard,
>
>> Thanks a lot for that tutorials. They look very interesting and I was
>> always curious how much work it would have been to implement something
>> like redports.org on top of Jenkins. But obviously my decision was
>> correct that jenkins would not fit in such a situation.
>>
>
> Could you clarify a bit more why you think Jenkins does not fit well there?
>
> I don't know how redports.org is designed and how it scales, but with
> Jenkins it's quite easy to create a package build farm for distributed
> building.

Redports is a public compile testing environment for FreeBSD ports. So like
Ports Tinderbox but with a nice multiuser GUI, cluster functionality for
scaling and an own Subversion tree for the users to commit their ports to.

Before I decided to write the code myself I had a closer look at Bitten and
Jenkins. Both could be made into what redports is now but they all have
their weak spots. Jenkins GUI looks very cluttered and is quite hard to
understand if you just want to manually schedule a few new jobs for your
ports as Joe Average. It's also quite hard to understand and complex as a
developer and administrator so I was concerned that fixing it if it breaks is
non trivial. Not to talk about all the special customizations that we need
which would require me to write extensions in Java and understand how
all that jenkins internals work.

Bitten looked simpler and less complex but would also work for standard
things but it got me on the right track to use Trac as webinterface and just
extend Trac with a custom plugin that includes a few simple pages to
have an overview of jobs and add new ones.

> Jenkins comes with lots of ready-to-use plugins as well, which makes
> it easier to integrate a particular thing easier as well and not
> re-invent the wheel.

Yeah that is nice and there is almost everything that you can think of but
none of them did what I needed. A simple web interface for average people
that don't want to learn Jenkins internals and is easily customizable. Probably
there is a plugin for that but I didn't find it. Writing some glue code around
tinderbox to schedule new jobs, checkout repositories and such stuff is
custom code anyway.


>> A more suitable place for jenkins would be automatic building our doc
>> tree on every commit. But I don't know if that doesn't already exist.
>
> Yep, that's one of the things we could use Jenkins for, but I would
> say we could use it for lots of other stuff as well :)

I'm sure we could. Examples?

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose: kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o] Error 1

[Bernhard Fröhlich]

On Sa., 15. Sep. 2012 12:38:32 CEST, O. Hartmann  
wrote:

> Updating emulators/virtualbox-ose on FreeBSD 10.0-CURRENT #1 r240515M:
> Fri Sep 14 23:15:34 CEST 2012 (amd), buildworld and buildkernel with
> CLANG (3.2) fails with the error shown below.
> 
> This also used to happen on   FreeBSD 9.1-PRERELEASE #0 r239768: Tue Aug
> 28 10:31:05 CEST 2012 (amd64), also CLANG world/kernel, but CLANG 3.1.
> 
> 
> 
> 
> In file included from
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/cpu-exec.c:32:
> In file included from
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/tcg/tcg.h:25:
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/tcg/i386/tcg-target.h:128:53:
> warning: unused parameter 'start'
>             [-Wunused-parameter]
> static inline void flush_icache_range(unsigned long start, unsigned long
> stop)
>                                                                               
>                          ^
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/tcg/i386/tcg-target.h:128:74:
> warning: unused parameter 'stop'
>             [-Wunused-parameter]
> static inline void flush_icache_range(unsigned long start, unsigned long
> stop)
>                                                                               
>                                                                  
> ^
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/cpu-exec.c:77:51:
> warning: unused parameter 'puc' [-Wunused-parameter] void
> cpu_resume_from_signal(CPUState *env1, void *puc)                             
>                 
>                                                     ^
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/cpu-exec.c:111:64:
> warning: unused parameter 'orig_tb' [-Wunused-parameter] static void
> cpu_exec_nocache(int max_cycles, TranslationBlock *orig_tb)                   
>       
>                                                                               
>                    ^
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/cpu-exec.c:873:44:
> warning: unused parameter 'start' [-Wunused-parameter] void
> tb_invalidate_page_range(target_ulong start, target_ulong end)                
>    
>                                                                 ^
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/cpu-exec.c:873:64:
> warning: unused parameter 'end' [-Wunused-parameter] void
> tb_invalidate_page_range(target_ulong start, target_ulong end)                
>    
>                                                                               
>                          ^ 53 warnings and 1
> error generated. kmk: ***
> [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/out/freebsd.amd64/release/obj/VBoxRemPrimary/cpu-exec.o]
> Error 1
> The failing command:
> @clang -c -O2 -g -pipe -Wall -Wextra -Wno-missing-field-initializers
> -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-long-long
> -Werror-implicit-function-declaration -Wno-variadic-macros -O2
> -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing
> -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN
> -DRT_USE_VISIBILITY_DEFAULT -fPIC -Wno-sign-compare
> -Werror-implicit-function-declaration -m64
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/Sun/crt
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/Sun
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/target-i386
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/tcg
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/fpu
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/out/freebsd.amd64/release/obj/VBoxRemPrimary
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/VBox/VMM/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler/tcg/i386
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/src/recompiler
> -I/usr/include -I/usr/X11R6/include -I/usr/local/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/out/freebsd.amd64/release
> -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS
> -DVBOX_WITH_HARDENING
> -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\"
> -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\"
> -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\"
> -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\"
> -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DIN_RING3
> -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DPIC -DIN_REM_R3
> -DREM_INCLUDE_CPU_H -DNEED_CPU_H -DLOG_USE_C99 -D_BSD -D__x86_64__
> -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.22/out/freebsd.amd64/release/obj/VBoxRemP

[Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

Hi virtualbox users!

I am very glad to be able to send out a VirtualBox 4.2.0 call for testers.
We've done a good job pushing many patches upstream before the
release this time so our port is much smaller and easier to handle.

The stability of 4.2.0 seems to be better than the past .0 releases so
our plan is to commit 4.2 to the portstree as soon as FreeBSD 9.1 is
out the door. Feedback from this CFT will tell us where we really are
so please also report positive feedback.

We are still looking for more people that can help with vbox maintenance
and development but the situation improved already since Mikhail
Tsatsenko and Ed Maste joined the team! Thanks a lot guys!! If you
are interested or have noticed a bug you can easily find us on IRC.


Please ensure that your Kernel sources match your running kernel before
building the virtualbox-ose-kmod port!

Changes since VirtualBox 4.1:
https://www.virtualbox.org/wiki/Changelog

VirtualBox 4.2.0 and 4.1.22 (legacy) Ports:
http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.0-20120920.tar.gz

IRC: #freebsd-vbox on Freenode


Bernhard on behalf of the new VirtualBox on FreeBSD Team!

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

On Thu, Sep 20, 2012 at 9:50 AM, Marek Salwerowicz  wrote:
> Hi,
>
> W dniu 2012-09-20 08:02, Bernhard Fröhlich pisze:
>>
>> Hi virtualbox users!
>>
>> I am very glad to be able to send out a VirtualBox 4.2.0 call for testers.
>> We've done a good job pushing many patches upstream before the
>> release this time so our port is much smaller and easier to handle.
>
>
>
> thanks for the release - I will do some tests and let you know about the
> results.
>
> By the way - can you tell me if there are any plans for releasing the
> Extension Pack for FreeBSD?
> I'd really like to have the Intel E1000 PXE support in virtual machine.
> So far now it doesn't work in my environment:
>
> s14% sudo VBoxManage list extpacks
> Extension Packs: 2
> Pack no. 0:   Oracle VM VirtualBox Extension Pack
> Version:  4.1.4
> Revision: 74291
> Description:  USB 2.0 Host Controller, VirtualBox RDP, PXE ROM with E1000
> support.
> VRDE Module:  VBoxVRDP
> Usable:   false
> Why unusable: Failed to locate the main module ('VBoxPuelMain')
> s14%

The Oracle Extension Packs are binary blobs and don't support FreeBSD yet.
If we can convince the vbox developers that FreeBSD support is worth the work
and brings them some money they will most likely also release extension
packs and provide binary packages for virtualbox at some point.

That is a longterm goal and nobody knows if we ever get to that point. When
I look back 3 years when we started with vbox on FreeBSD and compare that
to the current state then I think we have almost reached a point where FreeBSD
support is almost equivalent in feature parity and stability to MacOSX and
Linux support. Sure there are still some weak areas like the networking
implementation in FreeBSD but the linux kernel guys are also unhappy with the
vbox kernel module stability so there is no big difference.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

latest devel/kBuild-devel is included in the CFT tarball. Please use
that one. I know it
has about the same version number but that is because it's only a
snapshot without
a new release. I should have said that earlier but I simply forgot. Sorry.

vbox@ is the new maintainer of kBuild and kBuild-devel so there is no
need to inform
anyone. Update to kBuild-devel will be committed together with vbox 4.2 update.

-- 
Bernhard Froehlich
http://www.bluelife.at/


On Fri, Sep 21, 2012 at 12:35 PM, Daniel Braniss  wrote:
>> > great!
>> > now some question :-)
>> > where can I get latest kbuild?
>> > ...
>>
>> You need kBuild-devel from redports.org svn repository:
>>
>> svn co https://svn.redports.org/virtualbox/devel/kBuild-devel
>> # cd kBuild-devel && make deinstall install clean
>>
> thanks, btw, maybe the maintener of ports/devel/kBuild-devel should
> be informed?
>
> danny
>
>> --
>>  Mikhail
>> > ===>  Building for virtualbox-ose-4.2.0
>> > cd 
>> > /h/pobj/a/store-01/h/src/ports/emulators/virtualbox-cft-4.2.0/virtualbox-ose/work/VirtualBox-4.2.0
>> >  && /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local 
>> > VBOX_FREEBSD_SRC=/usr/src/sys /usr/local/bin/kmk -j 1
>> > Config.kmk:158: *** You must update kBuild! Requires kBuild revision 2577 
>> > or later, found 2546 (0.1.9998-r2546).  Stop.
>> >
>> > cheers,
>> > danny
>> >
>> >
>> > ___
>> > freebsd-ports@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

On Sa., 22. Sep. 2012 18:54:08 CEST, Marek Salwerowicz  wrote:

> Hi,
> 
> W dniu 2012-09-20 08:02, Bernhard Fröhlich pisze:
> > Bernhard on behalf of the new VirtualBox on FreeBSD Team!
> What happened with '--vnc' option of VBoxHeadless?
> 
> s14% VBoxHeadless --startvm test1 --vnc --vncport 5100 --width 800 
> --height 600
> Oracle VM VirtualBox Headless Interface 4.2.0_OSE
> (C) 2008-2012 Oracle Corporation
> All rights reserved.
> 
> VBoxHeadless: error: Unknown option: '--vnc'
> [..]
> 
> VBox was configured and installed with VNC support
> 
> log from ./configure:
> 
> [..]
> Checking for libvncserver: found version 0.9.9, OK.
> [..]

vnc is now implemented as a proper virtualbox plugin. This means it can be 
configured in the GUI and it's using the VRDE interface so you can run the vnc 
server and the VM in the QT4 interface at the same time.

-- 
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports - should I rename the updated distfile (tarball)?

[Bernhard Fröhlich]

On Do., 27. Sep. 2012 13:55:51 CEST, Anton Shterenlikht  
wrote:

> redports.org is good, thank you to whoever worked on it.

You're welcome.

> One question: the upstream for my port is non-existent,
> so rather then patch it, I'm updating the code itself.
> I then create a new tarball. It seems redports doesn't
> update the tarball every time I request a build.
> So it seems I have to update the version in Makefile
> each time and create a tarball with this new number.
> Is that so?

Redports uses a distfile cache so it only tries to download the distfile if 
it's not in the cache of that build machine yet. You could try to check 
bsd.ports.mk if there is a target that you can overwrite in your port where it 
does the distfile check.

-- 
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports: USA_RESIDENT=YES ?

[Bernhard Fröhlich]

On Fri, Sep 28, 2012 at 9:14 AM, Lars Engels  wrote:
> On Thu, Sep 27, 2012 at 04:36:34PM +0100, Chris Rees wrote:
>> On 27 Sep 2012 16:29, "Anton Shterenlikht"  wrote:
>> >
>> > What is the meaning of USA_RESIDENT=YES in redports build logs?
>> >
>>
>> The US government considers cryptography a weapon, so exporting it is
>> technically an offence.  Therefore, a declaration that you're a US resident
>> is required for strong cryptography, since the rest of the world is full of
>> terrorists and whatnot.
>
> Is that still so? IIRC that is no longer true since a few years.

Redports does generate packages but right now it does not allow to download
any package so even if that is still valid I don't think we are
"exporting" anything
except logfiles.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

Hi virtualbox users!

This is again a call for testers to get some feedback before we commit
VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you
should definitely update to 4.2.4 because they fixed quite a few serious
bugs upstream.

Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1
is out the door.

If you are interested in helping with virtualbox maintenance and
development or have noticed a bug you can easily find us on IRC.


Please update devel/kBuild-devel before updating any of the virtualbox
ports and ensure that your Kernel sources match your running kernel
before building the virtualbox-ose-kmod port.

Changes since VirtualBox 4.1:
https://www.virtualbox.org/wiki/Changelog

VirtualBox 4.2.4 and 4.1.22 (legacy) Ports:
http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz

IRC: #freebsd-vbox on Freenode


Bernhard on behalf of the new VirtualBox on FreeBSD Team!

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Tue, Oct 30, 2012 at 8:12 PM, Mike Jakubik
 wrote:
> On Tuesday 30 October 2012 5:16:14 AM Bernhard Fröhlich wrote:
>> Hi virtualbox users!
>>
>> This is again a call for testers to get some feedback before we commit
>> VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you
>> should definitely update to 4.2.4 because they fixed quite a few serious
>> bugs upstream.
>>
>> Bernhard on behalf of the new VirtualBox on FreeBSD Team!
>
>
> Hello, i have just tried to compile this on an up to date releng9 system.
>
> - Base GCC, compiles ok, works ok.
>
> - GCC47, fails, due to ugly -fno-format-extensions and  -fformat-extensions
> compiler hacks.

Patches are welcome but it's not supported from us yet and probably will
never be.

> - Clang, fails, details are below.

Clang does not support global registered variables so it's not supposed to
work.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Tue, Oct 30, 2012 at 10:04 PM, Mike Jakubik
 wrote:
> On Tuesday 30 October 2012 4:05:06 PM Mike Jakubik wrote:
>> On Tuesday 30 October 2012 3:56:29 PM Bernhard Fröhlich wrote:
>> > On Tue, Oct 30, 2012 at 8:12 PM, Mike Jakubik
>> >
>> > > Hello, i have just tried to compile this on an up to date releng9
>> > > system.
>> > >
>> > > - Base GCC, compiles ok, works ok.
>> > >
>> > > - GCC47, fails, due to ugly -fno-format-extensions and
>> > > -fformat-extensions compiler hacks.
>> >
>> > Patches are welcome but it's not supported from us yet and probably will
>> > never be.
>>
>> Thats a shame, i'll see if i can make it work, though im not an expert in
>> this field.

Default compiler for 10.0 will be CLANG from base but gcc 4.2 will still be in
base so we should be able to use that without additional work. That should
give us at least one more release cycle if we need it.

> This was apprantly already discussed by others two years ago.
>
> http://lists.freebsd.org/pipermail/freebsd-emulation/2010-July/007873.html
>
> I've modified Config.kmk to exclude those FreeBSD custom compiler options and 
> it
> continued to compile. Unforntunately it did fail again but for a different
> reason, it seems like getting this to work with an up to date version of gcc
> wouldnt be too hard by someone who knew what they were doing.

Andriy Gapon has some more recent patches for an older vbox version
that also work with gcc 4.6:
http://people.freebsd.org/~avg/vbox4-gcc45.patch

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Wed, Oct 31, 2012 at 8:42 AM, Mike Jakubik
 wrote:
> On 2012-10-30 08:07 PM, Jason Andresen wrote:
>>
>> On Oct 30, 2012, at 15:56, Bernhard Fröhlich  wrote:
>>
>>> Clang does not support global registered variables so it's not supposed
>>> to
>>> work.
>>
>>
>> Is this a feature?  Is there a reason why clang couldn't be updated
>> to support this if actual software is using it?
>
>
> It is a feature, but it appears to be a dirty one. Below is a link to a
> supposed Apple developer explaining the lack of this feature. I'm not a
> programmer but a humble sysadmin, so i do not know if this is true.
>
> http://nondot.org/sabre/LLVMNotes/GlobalRegisterVariables.txt


That problem also prevents QEMU from being build correctly with LLVM.

I'm just quoting the LLVM Users Manual:

"clang does not support global register variables; this is unlikely to be
implemented soon because it requires additional LLVM backend support."

http://clang.llvm.org/docs/UsersManual.html

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Wed, Nov 7, 2012 at 4:21 AM, Brandon Gooch
 wrote:
> On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich  wrote:
>> Hi virtualbox users!
>>
>> This is again a call for testers to get some feedback before we commit
>> VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you
>> should definitely update to 4.2.4 because they fixed quite a few serious
>> bugs upstream.
>>
>> Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1
>> is out the door.
>>
>> If you are interested in helping with virtualbox maintenance and
>> development or have noticed a bug you can easily find us on IRC.
>>
>>
>> Please update devel/kBuild-devel before updating any of the virtualbox
>> ports and ensure that your Kernel sources match your running kernel
>> before building the virtualbox-ose-kmod port.
>>
>> Changes since VirtualBox 4.1:
>> https://www.virtualbox.org/wiki/Changelog
>>
>> VirtualBox 4.2.4 and 4.1.22 (legacy) Ports:
>> http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz
>>
>> IRC: #freebsd-vbox on Freenode
>>
>>
>> Bernhard on behalf of the new VirtualBox on FreeBSD Team!
>>
>> --
>> Bernhard Froehlich
>> http://www.bluelife.at/
>
> I've updated to 4.2.4 on my system running HEAD. I've hit one annoying issue.
>
> I've been running the 4.2.0 Call for Testing for a while now, and it
> worked very well.
>
> After updating to 4.2.4 and updating the guest additions on several
> Linux guests, I've found that 3D acceleration is broken. The guest on
> which I didn't update the guest additions (so it's still running
> version 4.2.0 guest additions),  3D acceleration works great.
>
> This is a nuisance on systems which had some form of compositing
> enabled (e.g. compiz) because the login process (GDM in this case)
> just spins indefinitely waiting on (I presume) the window manager to
> fire up.
>
> Anyone else seeing this?

Hm haven't checked that recently. The only thing that changed between 4.2.0
and 4.2.2 from FreeBSD side was that we have enabled DRM in the additions
for FreeBSD guests but that should not affect Linux guests at all.

I will check if I can reproduce that.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: WireGuard for FreeBSD

[Bernhard Fröhlich]

On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld  wrote:
> We now have a release, so the full instructions for the packages are:
>
> 1. wireguard-tools, providing wg(8) and wg-quick(8)
> Runtime dependencies: bash, wireguard-go
> Buildtime dependencies: gmake, c compiler, libc
> Build: gmake -C src/tools WITH_WGQUICK=yes
> Install: gmake -C src/tools PREFIX=/usr/local install
> URL: https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180524.tar.xz
>
> 2. wireguard-go
> Runtime dependencies: libc
> Buildtime dependencies: gmake, go, dep
> Build: gmake
> Install: gmake PREFIX=/usr/local install
> URL: 
> https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20180524.tar.xz
>
> I believe decke is already working on a port in his repository.

Ports are already updated on github. I will do some final checks and
expect to commit
the wireguard ports to the official tree today.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: WireGuard for FreeBSD

[Bernhard Fröhlich]

On Thu, May 24, 2018 at 9:06 PM, Chris H  wrote:
> On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld" 
> said
>
>> Hi Chris,
>>
>> On Thu, May 24, 2018 at 3:38 PM, Chris H  wrote:
>> > I should have no trouble introducing Wireguard to the ports system
>> > today.
>>
>> I'm not a native fluent speaker of FreeBSDese, but my understanding is:
>> a) Bernhard committed the two new packages to ports today.
>> b) If you update ports with portsnap, you can build them locally.
>> c) If you run `pkg install wireguard`, it fails because the build
>> servers haven't gotten to them and won't for several days.
>>
>> Does your statement about "introducing WireGuard to the ports system"
>> mean that you intend to rectify (c) immediately, so we don't have to
>> wait several days for the build snapshot scripts to tick in cron? Or
>> is it mostly just related to not realizing (a)?
>
> Sigh...
> It was my understanding that when I stepped up to adopt WireGuard,
> and your ack to that. That *I* would be adding the port. I wasn't able
> to produce the port that same, or next day, as I am already Maintainer
> for nearly 150 ports. I have no trouble with that list, except that
> clang/llvm v5, and shortly after v6 became the default versions in $BASE.
> Which introduced a few pr(1)'s I needed to deal with.
> Now all the time I have spent researching, and staging to build the port
> have been laid to waste. Apparently you rescinded, and gave it to Bernhard.
> This project doesn't feel like a good match to me.
> No hard feelings, Bernhard. Have fun with the port.

(resend because the mailinglist blocked it)

Hi Chris,

I'm sorry that I was confusing people which was really not my
intention. I have also
seen your ACK to create the ports and replied to you in private to
offer my help. Then
I joined in IRC and just wanted to get an idea how far the FreeBSD
support was. I
ended up creating two very rough ports which did build but not pass
poudriere and
called it a day. I also did send you and the list a mail to avoid
duplicate work - and
hoped you take it as a base.

But I did not get any reply on the next day so I kept going and
finished the ports
yesterday with some good help from upstream.

Sorry for how that developed but I hoped you get in contact with
either me or upstream
which neither happened. We usually do not have the problem that too many people
want to help out so I did not expect that this will be a problem for anyone.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: WireGuard for FreeBSD

[Bernhard Fröhlich]

On Fri, May 25, 2018 at 12:24 AM, Chris H  wrote:
> On Thu, 24 May 2018 22:16:42 +0200 "Bernhard Froehlich" 
> said
>
>> Am 24.05.2018 21:06 schrieb Chris H :
>> >
>> > On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld"
>> > 
>> > said >
>> > > Hi Chris, > > > > On Thu, May 24, 2018 at 3:38 PM, Chris H
>> > >  wrote: > > > I should have no trouble 
>> > > introducing
>> > > Wireguard to the ports system today.
>> > > > > > I'm not a native fluent speaker of FreeBSDese, but my
>> > > > > > understanding is: > > a) Bernhard committed the two new packages 
>> > > > > > to ports
>> > > > > > today. > > b) If you update ports with portsnap, you can build 
>> > > > > > them locally.
>> > > > > > > > c) If you run `pkg install wireguard`, it fails because the 
>> > > > > > > > build > >
>> > > > > > servers haven't gotten to them and won't for several days. > > > > 
>> > > > > > Does your
>> > > > > > statement about "introducing WireGuard to the ports system" > > 
>> > > > > > mean that
>> > > > > > you intend to rectify (c) immediately, so we don't have to > > 
>> > > > > > wait several
>> > > > > > days for the build snapshot scripts to tick in cron? Or > > is it 
>> > > > > > mostly
>> > > > > > just related to not realizing (a)? > Sigh... > It was my 
>> > > > > > understanding that
>> > > > > > when I stepped up to adopt WireGuard, > and your ack to that. That 
>> > > > > > *I* would
>> > > > > > be adding the port. I wasn't able > to produce the port that same, 
>> > > > > > or next
>> > > > > > day, as I am already Maintainer > for nearly 150 ports. I have no 
>> > > > > > trouble
>> > > > > > with that list, except that > clang/llvm v5, and shortly after v6 
>> > > > > > became the
>> > > > > > default versions in $BASE. > Which introduced a few pr(1)'s I 
>> > > > > > needed to deal
>> > > > > > with. > Now all the time I have spent researching, and staging to 
>> > > > > > build the
>> > > > > > port > have been laid to waste. Apparently you rescinded, and gave 
>> > > > > > it to
>> > > > > > Bernhard. > This project doesn't feel like a good match to me. > 
>> > > > > > No hard
>> > > > > > feelings, Bernhard. Have fun with the port.
>> Hi Chris,
>>
>> I'm sorry that I was confusing people which was really not my intention. I
>> have also seen your ACK to create the ports and replied to you in private
>> to
>> offer my help. Then I joined in IRC and just wanted to get an idea how far
>> the FreeBSD support was. I ended up creating two very rough ports which
>> did
>> build but not pass poudriere and called it a day. I also did send you and
>> the
>> list a mail to avoid duplicate work - and hoped you take it as a base.
>>
>> But I did not get any reply on the next day so I kept going and finished
>> the
>> ports yesterday with some good help from upstream.
>>
>> Sorry for how that developed but I hoped you get in contact with either me
>> or
>> upstream which neither happened. We usually do not have the problem that
>> too
>> many people want to help out so I did not expect that this will be a
>> problem
>> for anyone.
>
> Ahem. OK thank you for the kind words, and intentions, Bernhard. Like I
> said;
> no hard feelings. If you've already gotten that far. You might as well
> finish.
> FWIW while you *did* indeed shoot me, and the list a couple of notes. I was
> never under the impression you were going to take it so far. Which
> *ultimately*
> left everyone concerned believing *you* were going to maintain it.
> I only mention it, in hopes all of us might use the --verbose switch in the
> future, in hopes of avoiding this sort of nonsense. :-) :-)
>
> Thanks again, Bernhard!
>
> --Chris
>
> P.S. just in case it wasn't clear; feel free to finish, and submit your
> work.
> P.P.S. Just so you (and everyone else) knows; I'm already working on the
> kernel module. Please keep in touch, should you also be interested, and have
> any work of your own.

Hi chris,

to be crystal clear about that. My motivation is not to be maintainer
of any specific
port or anything like that but only to have technology available on
FreeBSD that I
personally need and/or want.

Usually for more complex ports this did lead to team efforts on our porting work
which was also what I did expect to happen for wireguard. Well it
turned out to be
easier than thought and upstream was also very helpful so in the end
that was more
like a one day of work effort to get the basic ports.

Nevertheless I would still be very happy to increase the bus factor
and team up with
multiple people to maintain wireguard. I think there will be more work
to be done in the
near future for wireguard on FreeBSD where a team effort would speed
up things for
sure:

- we need to support FreeNAS and pfsense to get it into their package systems
- documentation is still needed because it differs a bit from upstream
documentation (Handbook page?)
- wireguard kernel module (can that work already be seen somewhere?
upstream will be interested for sure)
- rc script

Re: FreeBSD Port: multimedia/tvheadend

[Bernhard Fröhlich]

On Mon, May 28, 2018 at 9:03 PM 김종성  wrote:
>
> Hi decke,
>
> Just created a pull-request to fix DVR-related problems found while using the 
> FreeBSD port of tvheadend:
>
> https://github.com/tvheadend/tvheadend/pull/1125
>
> Please apply the patch to the port, if you think it's reasonable. Welcome any 
> comments about it.
>
> Thanks,
> JS

Hi Jongsung,

sorry that it took so long but i've finally committed it to the
FreeBSD port as well.

Thanks for the patch!

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: multimedia/tvheadend cannot service live TV after upgrading v4.2.7

[Bernhard Fröhlich]

On Tue, Oct 23, 2018 at 5:53 AM 김종성  wrote:
>
> Hi decke,
> tvheadend v4.2.7 has a merged commit 3895c923a FreeBSD: Fix recv problem if 
> no data received, which touches my previous merged commit 0d5c8efee tcp: fix 
> tcp_socket_dead() for FreeBSD. It makes the FreeBSD port of tvheadend unable 
> to service live TV, and reverted from the mainline. (f08bbef11 Revert 
> "FreeBSD: Fix recv problem if no data received.") Please apply this reverting 
> patch:
>
> commit f08bbef11c77a6a81d4e2bf974e36e54b0cd14d6
> Author: Jaroslav Kysela 
> Date:   Tue Oct 16 16:51:00 2018 +0200
>
> Revert "FreeBSD: Fix recv problem if no data received."
>
> This reverts commit 3895c923a3a959da05080831b8146c09ed143b00.
>
> diff --git a/src/tcp.c b/src/tcp.c
> index d15b4381f..5349784a4 100644
> --- a/src/tcp.c
> +++ b/src/tcp.c
> @@ -454,11 +454,8 @@ tcp_socket_dead(int fd)
>if (err)
>  return -err;
>  #ifdef PLATFORM_FREEBSD
> -  err = recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT);
> -  if (err < 0)
> +  if (recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT) < 0)
>  return -errno;
> -  else if (err == 0)
> -  return -EIO;
>  #else
>if (recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT) == 0)
>  return -EIO;
>
> Thank you
> JS

Thanks! Committed in r482966.

https://svnweb.freebsd.org/ports?view=revision&revision=482966

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: multimedia/tvheadend cannot service live TV after upgrading v4.2.7

[Bernhard Fröhlich]

Hi Jongsung,

sorry for the long delay! I was quite busy with other stuff.

The webui fixes in the other mail (and the included patch in this one)
seem to be
okay and I will commit them in a few minutes.

About the sendfile syscall can you point me to a patch that you mean?

I just found another kqueue fix which seems to be interesting:
https://github.com/tvheadend/tvheadend/commit/e3c8cb7dfd8de508a89d304cef5fe9b86bdc08c7

Thanks!


On Mon, Oct 29, 2018 at 9:25 AM 김종성  wrote:
>
> We need to re-apply my second patch related to sendfile syscall too. The 
> current tvheadend can't service recorded media properly.
>
> And I have another suggestion about web UI. I have seen abnormal behavior in 
> the EPG tab. The entire program list disapears when I click "Reset All" 
> button. This happens also when I type any search text and delete all. Linux 
> tvheadend users don't suffer this problem.
> However, I found a way to fix this problem by modifying 
> src/webui/static/app/epg.js:
>
> diff --git a/src/webui/static/app/epg.js b/src/webui/static/app/epg.js
> index 650ac9202..d00b76557 100644
> --- a/src/webui/static/app/epg.js
> +++ b/src/webui/static/app/epg.js
> @@ -1167,12 +1167,10 @@ tvheadend.epg = function() {
>  var value = c.getValue();
>
>  if (value.length < 1)
> -value = null;
> -
> -if (epgStore.baseParams.title !== value) {
> +delete epgStore.baseParams.title;
> +else if (epgStore.baseParams.title !== value)
>  epgStore.baseParams.title = value;
> -epgView.reset();
> -}
> +epgView.reset();
>  });
>
>  epgFilterFulltext.on('check', function(c, value) {
>
> But I don't know whether it's correct way and why it works, because I totally 
> don't know about web programming. Can anybody review this patch?
>
>
> 2018년 10월 25일 (목) 오후 8:49, Bernhard Fröhlich 님이 작성:
>>
>> On Tue, Oct 23, 2018 at 5:53 AM 김종성  wrote:
>> >
>> > Hi decke,
>> > tvheadend v4.2.7 has a merged commit 3895c923a FreeBSD: Fix recv problem 
>> > if no data received, which touches my previous merged commit 0d5c8efee 
>> > tcp: fix tcp_socket_dead() for FreeBSD. It makes the FreeBSD port of 
>> > tvheadend unable to service live TV, and reverted from the mainline. 
>> > (f08bbef11 Revert "FreeBSD: Fix recv problem if no data received.") Please 
>> > apply this reverting patch:
>> >
>> > commit f08bbef11c77a6a81d4e2bf974e36e54b0cd14d6
>> > Author: Jaroslav Kysela 
>> > Date:   Tue Oct 16 16:51:00 2018 +0200
>> >
>> > Revert "FreeBSD: Fix recv problem if no data received."
>> >
>> > This reverts commit 3895c923a3a959da05080831b8146c09ed143b00.
>> >
>> > diff --git a/src/tcp.c b/src/tcp.c
>> > index d15b4381f..5349784a4 100644
>> > --- a/src/tcp.c
>> > +++ b/src/tcp.c
>> > @@ -454,11 +454,8 @@ tcp_socket_dead(int fd)
>> >if (err)
>> >  return -err;
>> >  #ifdef PLATFORM_FREEBSD
>> > -  err = recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT);
>> > -  if (err < 0)
>> > +  if (recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT) < 0)
>> >  return -errno;
>> > -  else if (err == 0)
>> > -  return -EIO;
>> >  #else
>> >if (recv(fd, NULL, 0, MSG_PEEK | MSG_DONTWAIT) == 0)
>> >  return -EIO;
>> >
>> > Thank you
>> > JS
>>
>> Thanks! Committed in r482966.
>>
>> https://svnweb.freebsd.org/ports?view=revision&revision=482966
>>
>> --
>> Bernhard Froehlich
>> http://www.bluelife.at/



-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ansible playbooks for building a poudriere test system

[Bernhard Fröhlich]

On Mon, Sep 23, 2019 at 10:27 AM Matthew Seaman  wrote:
>
> Hi,
>
> I put this together as the basis of the class I gave at EuroBSDCon a few
> days ago, and I thought I'd share it as it might prove useful:
>
>https://github.com/infracaninophile/p4pm
>
> This should be able to take an 'as installed' FreeBSD machine with just
> a local user account added, or the default config of a VM from AWS,
> Azure etc. upto a fully configured poudriere build box.  Currently it
> sets up jails suitable for running build tests on updated ports, but
> turning it into a system for managing a private ports repo should be
> pretty simple.

Sounds like a good base for caronade which would integrate with github
and trigger the poudriere build.

https://code.bluelife.at/decke/caronade

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: The state of redports

[Bernhard Fröhlich]

On Sa., 17. Nov. 2012 01:56:01 CET, Bryan Drewery  wrote:

> On 11/16/2012 6:41 PM, Shane Ambler wrote:
> > I haven't got a response from redports servers for a while now.
> > 
> > Has redports closed it's doors? Having hardware issues?
> > 
> 
> It's a temporary issue. decke@ might provide more details.

Yeah, redports is down since almost a week now and it looks like some 
infrastructure problem/migration whatsoever. I also cannot access the boxes 
right now so I need to wait until things get fixed before I can jump in.

If you follow the mailing lists you'll notice that quite a few systems are down 
right now and people are doing their best to fix them.

Be assured that redports will come back!

-- 
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: The state of redports

[Bernhard Fröhlich]

On Di., 27. Nov. 2012 04:38:39 CET, meta  wrote:

> I know the work continues on rebuilding infrastructure.
> Is priority low to reopen redports than other infrastructure?

The bottleneck right now are people that can do the security audit and verify 
carefully which machines are safe and which we need to setup from scratch.

> Could anybody tell me when redports will be back?
> In a few days? weeks? months? or almost a year?

I honestly don't know and I'm unable to make an educated guess so all I can do 
is to inform people once I have some news. But we are surely talking about days 
or weeks because otherwise I'll reactivate my box in the basement ...

Sorry that this incident knocked redports down for such a long time. Redports 
still isn't critical enough to the project that it gets dealt with immediately 
so the plan is clear. We need to provide services to the src people and 
something nice for cluster admins, security teams and core to make them feel 
the pain like we do when redports is offline.

-- 
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

On Fri, Sep 21, 2012 at 4:43 PM, Daniel Braniss  wrote:
> I install vboxdrv.ko in /usr/local/modules via:
> cd virtualbox-ose-kmod
> make KMODDIR=/usr/local/modules install
> but when installing in virtualbox-ose
> there is no KMODDIR, and hence make install fails

Sorry for that very long response time. I have made a patch that should fix that
issue but haven't yet tested it so if you can please give that a try.

https://github.com/decke/freebsd-vbox/commit/cd1a793d24fb27525830275bea5cce2cfb4eb3fd

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose-kmod: always use compiler "cc" which is on my basesystem CLANG 3.2 (FreeBSD 10.0)

[Bernhard Fröhlich]

Am 30.12.2012 15:15 schrieb "O. Hartmann" :
>
> Port emulators/virtualbox-ose-kmod is known not to compile with CLANG
> 3.1/3.2. Therefor, it should be compiled with gcc.
>
> Either setting USE_GCC=4.6+ or USE_GCC=any in the port's makefile or by
> setting a global file with the directive
>
> # emulators/virtualbox-ose
> .if ${.CURDIR:M*/emulators/virtualbox-ose*}
> USE_GCC=4.6+
> .endif
>
>
> do not work! Compiling the port is always nailed down to use "cc" which
> is CLANG 3.2 by default.

Vbox from ports can only be compiled with base GCC 4.2 so USE_GCC=any
should be right but I've never tested it. You could also try the new vbox
from github which includes a patch to build correctly with GCC 4.6.

http://github.com/decke/freebsd-vbox
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose failing to build, 8.2-p9 on amd64

[Bernhard Fröhlich]

Looks like your libsdl version is either very old or too new. Could you
please check which libsdl version you have installed?
Am 06.01.2013 03:10 schrieb "Matthew Pounsett" :

>
> I'm having a problem getting virtualbox to build on an 8.2-R-p9 box.  The
> compile is failing with the below pasted error.  I've made sure that all of
> the ports that virtualbox depends upon are up to date.
>
> > uname -a
> FreeBSD masked.com 8.2-RELEASE-p9 FreeBSD 8.2-RELEASE-p9 #0: Mon Jun 11
> 23:00:11 UTC 2012 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64
>
> My make.conf is simple:
>
> MAKEFLAGS="-j3"
> WITH_APACHE2="yes"
> # added by use.perl 2012-12-04 17:16:34
> PERL_VERSION=5.14.2
>
> I have tried commenting out the MAKEFLAGS entry and recompiling, but that
> doesn't help.Does anyone have thoughts on what the problem is, or
> suggestions for troubleshooting?
>
> Thanks in advance.
>
>
>
> kBuild: Compiling VBoxSDL -
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:
> In member function 'virtual nsresult
> VBoxSDLConsoleEventListener::HandleEvent(PRUint32, IEvent*)':
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:543:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:
> In function 'int TrustedMain(int, char**, char**)':
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:2069:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:2074:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:2865:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:2880:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:
> In function 'uint16_t Keyevent2Keycode(const SDL_KeyboardEvent*)':
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:3351:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:
> In function 'void SetPointerShape(const PointerShapeChangeData*)':
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:4596:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Frontends/VBoxSDL/VBoxSDL.cpp:4615:
> error: 'struct SDL_SysWMinfo' has no member named 'info'
> kmk: ***
> [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxSDL/VBoxSDL.o]
> Error 1
> The failing command:
> @g++ -c -O2 -fPIC -g -pipe -Wshadow  -Wno-long-long -Wno-variadic-macros
> -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive
> -fexceptions -frtti -O2 -mtune=generic -fno-omit-frame-pointer
> -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=hidden
> -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxSDL
> -I/usr/include -I/usr/X11R6/include -I/usr/local/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/string
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom
> -I/usr/
>  
> ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/ipcd
> -I/usr/local/include/SDL -I/usr/local/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/include
> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release
> -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS
> -DVBOX_WITH_HARDENING -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64
> -D__AMD64__ -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\"
> -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\"
> -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbo

Re: emulators/virtualbox-ose failing to build, 8.2-p9 on amd64

[Bernhard Fröhlich]

Great. Thanks for reporting your results.
Am 06.01.2013 20:23 schrieb "Matthew Pounsett" :

>
> On 2013/01/06, at 04:46, Matthew Pounsett wrote:
>
> >
> > On 2013/01/06, at 02:48, Bernhard Fröhlich wrote:
> >
> >> Looks like your libsdl version is either very old or too new. Could you
> >> please check which libsdl version you have installed?
> >
> > 1.2.15-_2,2.  It's the current ports version (as of this afternoon when
> I updated my ports tree).
> >
> Ah.. I found the problem.  The libsdl port config file had an old
> WITHOUT_X11 it was holding on to.. I got rid of that, rebuilt, and
> virtualbox compiles fine now.   Thanks for the lead!
>
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[HEADS-UP] Ports QAT and redports.org are back!

[Bernhard Fröhlich]

Hello Porters,

I'm happy to announce that our Ports QAT and redports.org are
back in action. Both systems were taken offline due to the incident
in November last year even though they were not directly affected.
A security review and a reinstallation from scratch including some
changes were performed to improve security. The resulting user
visible changes are:

- All password hashes on redports.org were deleted so you need
to use the "Password lost" functionality to get a new password
via mail. Beware the email check is case sensitive and I have seen
many people use "@FreeBSD.org" for their email addresses.
If you have problems or forgotten your password please contact me.

- Please recover your account by 28th February because after that
all non recovered accounts will be deleted. (cleanup)

- Registration on redports.org is temporary disabled. It will be re-
enabled in March.

- Ports QAT and redports.org are separate machines now. Ports
QAT is available only via https on his own subdomain
https://qat.redports.org/

- Beware that QAT mails are sent do po...@freebsd.org mailinglist
so they are now public.

- svn.redports.org is only available via https - http is gone.

- IPv6 is currently unavailable but should hopefully come back in
a few weeks.

- IRC bot is gone. Not sure yet if we will be able to bring it back.

- Two additional backends from the Foundation are currently being
prepared. They should go online pretty soon.


Thanks a lot to everyone involved in getting both systems back and
especially to Brad Davis for all of his work behind the scenes!
Sorry to all users that it took us 3 months to get back in action and
thanks that you all were so patient while we sorted that out.

Contact:
https://redports.org/
https://qat.redports.org/

https://twitter.com/redports
IRC: #redports on freenode
https://groups.google.com/group/redports

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox patch

[Bernhard Fröhlich]

On Tue, Mar 12, 2013 at 4:17 PM, Konstantin Belousov
 wrote:
> On Tue, Mar 12, 2013 at 09:01:43AM -0300, Sergio de Almeida Lenzi wrote:
>> Em Seg, 2013-03-11 ??s 10:28 +0100, Ferenc Balku escreveu:
>>
>> > Hi Sergio!
>> >
>> > Awfully sorry to disturb You, but I have found this link via Google
>> > http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/081979.html
>> > and can not find the patch to download a make VBox work again on our
>> > FBSD10 test server.
>> >
>> > Can You please send me a link to download the patch.
>> >
>> > Thanks in advance,
>> >
>> > Best Regards
>> >
>> > Ferenc Balku
>>
>>
>> No problem   I was "travel business...
>> here is the patch,
>> the list does not allow attach files...
>>
>> go to the /usr/ports/emulators/virtualbox-ose-kmod,
>> put the fix in the "files" directory with a name like ==>
>> patch-the-freebsd-kernel
>> and do a make clean install
>> ==
>> --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h.orig
>> 2012-12-19 16:27:29.0 -0200
>> +++ src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h 2013-03-09
>> 14:42:18.924039639 -0300
>> @@ -50,6 +50,7 @@
>>  #include 
>>  #include 
>>  #include 
>> +#include 
>>  #include 
>>  #include 
>>  #include 
>> @@ -70,6 +71,12 @@
>>  #include 
>>  #include 
>>
>> +/*
>> +   fix VM_OBJ_LOCK
>> +*/
>> +#defineVM_OBJECT_LOCK(o) VM_OBJECT_RLOCK(o)
>> +#defineVM_OBJECT_UNLOCK(o) VM_OBJECT_RUNLOCK(o)
>
> This is definitely wrong. For the blind substitution, you should
> use VM_OBJECT_WLOCK/VM_OBJECT_WUNLOCK.

It would be great if someone could come up with a proper patch.
All I've seen so far looks wrong or hackish and I cannot add that
to the port nor send it upstream to get it fixed for future releases.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Updating curl

[Bernhard Fröhlich]

On Sun, Mar 24, 2013 at 1:53 PM, Jerry  wrote:
> On Sun, 24 Mar 2013 13:10:25 +0100
> olli hauer articulated:
>
> [snip}
>
>> Just a quick question.
>> How many ports do you maintain?
>
> Three, very simple ports.
>
>> I have to ask this question because it looks like you are always
>> coming up with the same copy pasted text snippets (do you have them
>> as text blocks in vim or emacs?)
>
> I have never created a boilerplate if that is what you are referring to.
>
>> If you are willing to do the maintenance of an actual curl port please
>> come up with an patch and request maintainer ship.
>
> I am actually thinking about updating curl on my system and no I would
> not release it since I am (1) not the maintain of said port, and (2) I
> don't have the time to actively maintain it. Which brings us back to my
> original statement, that being that if the current maintainer is not
> going to properly maintain the port than they should publicly state
> that fact which would allow another individual with sufficient time and
> skill to do so.
>
> If you remember a few months ago, there was a discussion as to why
> "Bash" lingered on for months, actually a year, with numerous patches
> being issued by the Bash author yet never being included in the port's
> system. Finally, another user created a "devel" port. Perhaps that is
> the proper way to handle this problem. "Postfix", probably the best
> maintained port in the entire system. has both a "stable" release and a
> "current" release in the ports system. I will agree that
> "sa...@freebsd.org" is probably an over achiever, but it is an example
> of what can be accomplished, and in virtual real time no less, when
> someone dedicates themselves to a task.

Sorry, but that is the absolutely wrong approach. The way it works is by
contributing not by keeping stuff in your hands and telling other that they
should come up with a solution.
If a port maintainer is unavailable for some time and unable to update the
port himself then it would be the best way to contact him if he has
something that you can help with. If he does not respond prepare an
update yourself, test it and verify that it works fine and then submit the
patch as PR. Then some committer will have a look and either the
maintainer approves it or it becomes a maintainer timeout and after that
the patch is committed.

If you talk to the maintainer and he feels that you already care more
about the port than he does I'm pretty sure he will offer to pass
maintainership to you. If a maintainer is unavailable for a longer period
(multiple maintainer timeouts) then the port maintainer will be reset
anyway and can be adopted.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Kernel panic CURRENT r248596 at virtualbox-ose-kmod module load

[Bernhard Fröhlich]

On Mon, Mar 25, 2013 at 1:03 AM, Ivan Klymenko  wrote:
> В Sun, 24 Mar 2013 14:05:07 +0200
> Konstantin Belousov  пишет:
>
>> On Sat, Mar 23, 2013 at 01:26:27PM +0200, Ivan Klymenko wrote:
>> > I have
>> > uname -a
>> > FreeBSD nonamehost 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248596: Fri
>> > Mar 22 01:17:08 EET 2013
>> > ivan@nonamehost:/usr/obj/usr/src/sys/GENERIC  amd64
>> >
>> > I updated the ports tree to r314921 and recompiled
>> > virtualbox-ose-kmod
>> >
>> > After load the module a have kernel panic.
>> >
>> > Panic  String:  Lock  vm  object  not  exclusively   locked   @
>> > /usr/src/sys/vm/vm_page.c:1396
>> >
>> > http://pkgupdate.nevosoft.ru/backtrace.txt
>>
>> This looks like a vbox issue, the driver did not properly locked
>> the object passed to the vm_page_alloc_contig().
>>
>> If you want this fixed, you probably need to look up the code
>> yourself, compiling the vbox kld with debugging, finding the
>> offending call to vm_page_alloc_contig() and looking around it to see
>> which object is passed and why it is not locked.
>
> The problem is that port commiter did not listen your advice:
> http://docs.freebsd.org/cgi/mid.cgi?20130312151751.GJ3794
>
> and used in the patch is not the functions that need
> http://svnweb.freebsd.org/ports/head/emulators/virtualbox-ose-kmod/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd_VM_OBJECT_RENAME.c?r1=314794&r2=314796
>
> I replaced the all function "VM_OBJECT_RLOCK" on "VM_OBJECT_WLOCK"
> and
> "VM_OBJECT_RUNLOCK" on "VM_OBJECT_WUNLOCK"
>
> and the kernel panic ceased.
>
> Thanks. This problem is solved.

Thanks a lot! I've fixed it in the port now. Would be great if you could verify
that it's correct now.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of packages

[Bernhard Fröhlich]

Am 26.03.2013 19:20 schrieb "grarpamp" :
>
> > This may not have made it out in this list, the latest announcement is
> > here http://www.freebsd.org/news/2012-compromise.html#update20130323
>
> It's nice to see something like redports. It can be helpful to those using
> ports to diagnose their local builds against the output of a formal
sandbox
> service for the project. It would be cool if the logs, build hiers and
packages
> from such a buildbot were accessible. They'd obviously always be in flux
but
> still useful to see.

Redports is very bad for providing packages because of all the frequent
changes and the "chaotic nature" of such a system. Additionally the
security considerations made clear that redports should never provide any
binary data to users to minimize risk in case of a potential security
incident.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Status of packages

[Bernhard Fröhlich]

On Wed, Mar 27, 2013 at 5:37 PM, grarpamp  wrote:
>>> It's nice to see something like redports. It can be helpful to those using
>>> ports to diagnose their local builds against the output of a formal
>>> sandbox
>>> service for the project. It would be cool if the logs, build hiers and
>>> packages
>>> from such a buildbot were accessible. They'd obviously always be in flux
>>> but
>>> still useful to see.
>
>> Redports is very bad for providing packages because of all the frequent
>> changes and the "chaotic nature" of such a system. Additionally the security
>> considerations made clear that redports should never provide any binary data
>> to users to minimize risk in case of a potential security incident.
>
> 'formal/project/service' and 'flux' were attempts at covering this. Another
> partial example might be pointyhat, the logs are viewable, but not the
> output file trees.
> The 'security' aspect would just seem whether the builds come
> from the main repo and are built in a pretty automated sandbox, or
> from joe's working tree in their own slush account.

No. The security concerns are that some "attacker" could infect binaries
and add dangerous code if he manages to break out of a jail or place
malicious code in some packages that are used as dependencies. Due to
the nature of redports many jobs by a lot of people are build in parallel and
ports depend on each other so you cannot trust the machine anymore and
the only way to proceed would be by wiping the box and restarting from
scratch. Since the packages are not shared accross multiple machines nor
made available to users the risk is that the machine has to be wiped but it
could never infect any user.
In addition to that redports does a lot to make sure that user modified
packages are not reused and environments are cleaned after each build
but nobody says it's impossible.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org No address record

[Bernhard Fröhlich]

On Fri, Apr 12, 2013 at 5:52 PM, Fernando Apesteguía
 wrote:
> Hi,
>
> I'm getting a "No address record" error[1] trying to build cad/openvsp in
> redports.
> It builds fine in my local machine and I can access the URL with the
> browser too.
>
> What am I missing?
>
> Thanks in advance.
>
> [1]
> https://redports.org/~fernape/20130412153229-03742-113174/openvsp-2.2.3.log

That is a known limitation of the new redports setup. The long story
is that the new redports backends are IPv6 only machines now in a
private IPv6 address space and their only internet access is via an
Squid proxy that allows FTP/HTTP/HTTPS.

Since our fetch(1) does not support proxies for HTTPS connections
it tries to lookup the domain himself and fails because it does not
have a DNS server or direct internet access. So in the end it is a
bug or missing feature of our fetch. I've CCD des@ just in case he
has a good idea.

The best way to workaround that right now is to add an HTTP or FTP
mirror and we should add one for GITHUB in portstree because that
seems to be one of the most affected one.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFH] FreeBSD 10 and ports

[Bernhard Fröhlich]

On Tue, Jun 11, 2013 at 1:21 PM, Shane Ambler  wrote:
> On 11/06/2013 16:20, Martin Wilke wrote:
>
>> As we all know FreeBSD 10 brings a new compiler along, and for that
>> we need to get ports on the right track. I have done several exp-runs
>> on the current src and we still have a lot of fallouts. We would like
>> to ask you to have a look [1] at the failed ports and help to fix
>> them. We will start this week an i386 exp-run to see how the status
>> is.
>
>
> For those of us running 9.1 what is the best way to test?
> I previously had little luck compiling in a 10-current tinderbox.
>
> I see that one of my ports is failing with 10 and clang 3.3. I know it
> compiles with clang 3.1 on 9.1. Is using 3.4 from clang-devel a useful test
> compiler?

If you have a redports.org account you can use the 10-CURRENT environments
which are running HEAD from 29th of May. Otherwise you can always register
yourself an account and ping me in IRC until I activate it.

--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFH] FreeBSD 10 and ports

[Bernhard Fröhlich]

Am 11.06.2013 21:22 schrieb "Konstantin Belousov" :
>
> On Tue, Jun 11, 2013 at 02:50:03PM +0800, Martin Wilke wrote:
> >
> > Dear All,
> >
> > As we all know FreeBSD 10 brings a new compiler along, and for that we
need to get ports on the right
> > track. I have done several exp-runs on the current src and we still
have a lot of fallouts. We
> > would like to ask you to have a look [1] at the failed ports and help
to fix them. We will start this week
> > an i386 exp-run to see how the status is.
> >
> > Thanks for your time.
> >
> > - Martin on behalf of portmgr
> >
> > [1]http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-10-exp-latest/
>
> Didn't a sort of consensus when switching to clang for base was
> discussed, was that ports would start use a port-provided version of gcc
> ? The adoption of the ports gcc was stalled due to the unability to make
> exp-runs, AFAIK.
>
> What you are proposing is de-facto forking the whole open-source code
> base. This cannot work, and in fact steals the FreeBSD resources for
> something which has absolutely no relevance for FreeBSD project.
>
> Ports should not be forced to use clang, either a ports gcc work
> should be finished, or cc in HEAD switched back to gcc.  This is
> de-facto blocker for the 10.0.

Yes we are working on that and though it's still in an early phase we
already know that we have to switch the full toolchain - which is a lot of
work.
This project can be seen as a midterm goal but it's unsure yet if we can
finish it before 10.0 but we will find out pretty soon.

In the meantime bapt and a few others have managed to fix quite a few ports
and managed to build a high number of ports with clang 3.3 already. So it
does not look that unrealistic anymore.

There has been no decision yet what the right way to proceed is but fixing
stuff for clang has proven to be worth the effort because newer gcc seems
to hit quite similar problems.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Are ports supposed to build and run on 10-CURRENT?

[Bernhard Fröhlich]

On Fri, Jun 14, 2013 at 2:36 PM, Michael Gmelin  wrote:
> On Thu, 13 Jun 2013 08:24:18 +0200
> Matthias Apitz  wrote:
>
>> El día Thursday, June 13, 2013 a las 08:07:14AM +0200, Eitan Adler
>> escribió:
>>
>> > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin 
>> > wrote:
>> > > So my question is: Are we port maintainers now really supposed to
>> > > make ports work with CURRENT?
>> >
>> > This is generally up to the maintainer; however many committers run
>> > -CURRENT and test on that by default.
>>
>> This was a widely general question and a general answer too;
>> I'm afraid that not all committers run tests with -CURRENT and on both
>> architectures (amd64 and i386);
>>
>> at least for KDE4 I can confirm that it is unable to build on -CURRENT
>> r250588 i386 due to:
>>
>> 1. certain required ports does not compile with clang
>> 2. for kdelibs4 (and others) the tool automoc4 SIGSEGV randomly (i.e.
>> for different source files and if you run it again it works)
>>
>> all this on a SVN clean ports tree;
>>
>> the current situation with CURRENT/clang/ports is highly a concern;
>>
>>   matthias
>
> To be perfectly honest, the fact that some committers seem to *solely*
> test on CURRENT seems like bad QA practice to me.

This is true and also the reason why ports on CURRENT were always not
supported but only on best effort basis. This is not only the responsibility
of ports people but ALSO each and every src committer. We usually just
have to catch up things that change on current and break a number of ports.

Things like changing the default compiler, changing version numbers to
something that break each and every autoconf dependent port are just
the well known problems. Many ports break because of smaller changes
in the toolchain and libraries and it takes some time to fix all affected ports.
If that is something you don't want then CURRENT is not suitable for you.

--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox 4.2.14 unusable

[Bernhard Fröhlich]

Am 08.07.2013 20:15 schrieb "Mikhail Tsatsenko" :
>
> 2013/7/8 Jimmy Kelley :
> > On Mon, Jul 08, 2013 at 12:40:16PM -0300, Sergio de Almeida Lenzi wrote:
> >> Yes it is broken,
> >>
> >> the logic that finds how much real memory is there in the FreeBSD
> >> is broken, reports ZERO..
> >>
> >> There is a Problem Report and a person that
> >> says will fix it, 2 weeks ago...
> >>
> >> I am using the last version 4.2.12 that works
> >>
> >> I am still waiting for the fix...
> >>
> >>
> >> Sergio
> >>
> >
> > I did a search on the Freebsd PRs (
http://www.freebsd.org/cgi/query-pr-summary.cgi) and
> > cannot find anything that seems to reference this problem.  Would you
know the PR number?
> > Or was this just some discussion on the mailing list?
> >
> > I'll file an offical PR if there isn't one.
> >
> > Jimmy
> There is no PR for this problem.
> As far as I understand memory calculation is still broken on CURRENT.
> And I suspect it is a build-time  not runtime bug.
> Can anybody who is facing the problem send me a full build log of the
> virtualbox-ose port from affected machine for investigation please.

There was a PR ports/180086 that was also mentioned in the commit.

You could try the patch in the mail and see if it helps.
http://lists.freebsd.org/pipermail/svn-ports-all/2013-July/024215.html
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox 4.2.14 unusable

[Bernhard Fröhlich]

On Mon, Jul 8, 2013 at 11:03 PM, Jimmy Kelley  wrote:
> On Mon, Jul 08, 2013 at 10:14:44PM +0400, Mikhail Tsatsenko wrote:
>> 2013/7/8 Jimmy Kelley :
>> > On Mon, Jul 08, 2013 at 12:40:16PM -0300, Sergio de Almeida Lenzi wrote:
>> >> Yes it is broken,
>> >>
>> >> the logic that finds how much real memory is there in the FreeBSD
>> >> is broken, reports ZERO..
>> >>
>> >> There is a Problem Report and a person that
>> >> says will fix it, 2 weeks ago...
>> >>
>> >> I am using the last version 4.2.12 that works
>> >>
>> >> I am still waiting for the fix...
>> >>
>> >>
>> >> Sergio
>> >>
>> >
>> > I did a search on the Freebsd PRs 
>> > (http://www.freebsd.org/cgi/query-pr-summary.cgi) and
>> > cannot find anything that seems to reference this problem.  Would you know 
>> > the PR number?
>> > Or was this just some discussion on the mailing list?
>> >
>> > I'll file an offical PR if there isn't one.
>> >
>> > Jimmy
>> There is no PR for this problem.
>> As far as I understand memory calculation is still broken on CURRENT.
>> And I suspect it is a build-time  not runtime bug.
>> Can anybody who is facing the problem send me a full build log of the
>> virtualbox-ose port from affected machine for investigation please.
>>
>> ___
>> > freebsd-ports@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>>
>>
>>
>> --
>> Mikhail
>
> Attached is my build log; I'm running 10-CURRENT i386.  I see the patch files 
> commited for this
> problem with VBox 4.2.14 (PR #180086) on my machine, but I have upgraded my 
> ports tree since
> and have the newer 4.2.16 version that I'm building.

Please try the patch from that mail and see if it helps. From the
reports it looks reasonable to say
that the currently committed patch works only on amd64. So far the
reports where it doesn't work
are all on i386 and this matches with the description of the fix in the mail.

http://lists.freebsd.org/pipermail/svn-ports-all/2013-July/024215.html

--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox 4.2.14 unusable

[Bernhard Fröhlich]

On Wed, Jul 10, 2013 at 1:09 AM, Jimmy Kelley  wrote:
> On Tue, Jul 09, 2013 at 01:34:59PM +0200, Bernhard Fröhlich wrote:
>> On Mon, Jul 8, 2013 at 11:03 PM, Jimmy Kelley  wrote:
>> > On Mon, Jul 08, 2013 at 10:14:44PM +0400, Mikhail Tsatsenko wrote:
>> >> 2013/7/8 Jimmy Kelley :
>> >> > On Mon, Jul 08, 2013 at 12:40:16PM -0300, Sergio de Almeida Lenzi wrote:
>> >> >> Yes it is broken,
>> >> >>
>> >> >> the logic that finds how much real memory is there in the FreeBSD
>> >> >> is broken, reports ZERO..
>> >> >>
>> >> >> There is a Problem Report and a person that
>> >> >> says will fix it, 2 weeks ago...
>> >> >>
>> >> >> I am using the last version 4.2.12 that works
>> >> >>
>> >> >> I am still waiting for the fix...
>> >> >>
>> >> >>
>> >> >> Sergio
>> >> >>
>> >> >
>> >> > I did a search on the Freebsd PRs 
>> >> > (http://www.freebsd.org/cgi/query-pr-summary.cgi) and
>> >> > cannot find anything that seems to reference this problem.  Would you 
>> >> > know the PR number?
>> >> > Or was this just some discussion on the mailing list?
>> >> >
>> >> > I'll file an offical PR if there isn't one.
>> >> >
>> >> > Jimmy
>> >> There is no PR for this problem.
>> >> As far as I understand memory calculation is still broken on CURRENT.
>> >> And I suspect it is a build-time  not runtime bug.
>> >> Can anybody who is facing the problem send me a full build log of the
>> >> virtualbox-ose port from affected machine for investigation please.
>> >>
>> >> ___
>> >> > freebsd-ports@freebsd.org mailing list
>> >> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> >> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>> >>
>> >>
>> >>
>> >> --
>> >> Mikhail
>> >
>> > Attached is my build log; I'm running 10-CURRENT i386.  I see the patch 
>> > files commited for this
>> > problem with VBox 4.2.14 (PR #180086) on my machine, but I have upgraded 
>> > my ports tree since
>> > and have the newer 4.2.16 version that I'm building.
>>
>> Please try the patch from that mail and see if it helps. From the
>> reports it looks reasonable to say
>> that the currently committed patch works only on amd64. So far the
>> reports where it doesn't work
>> are all on i386 and this matches with the description of the fix in the mail.
>>
>> http://lists.freebsd.org/pipermail/svn-ports-all/2013-July/024215.html
>>
>> --
>> Bernhard Froehlich
>> http://www.bluelife.at/
>
> Thanks for point out that old message.  I applied that updated patch and it 
> works now.
> The code is incorrectly assuming a 64-bit size for querying the hw.physmem 
> sysctl on
> a 32-bit system.
>
> Jimmy
>

The fix has now been committed to the port so virtualbox-ose 4.2.16_1
should work correctly
now.

--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports: error in dependency pkg-1.1.4_1.txz, exiting

[Bernhard Fröhlich]

Am 20.07.2013 01:23 schrieb "Anton Shterenlikht" :
>
> https://redports.org/~mexas/2013071921-42286-133205/libtool-2.4.2.log
>
> My port is actually astro/xearth, which,
> I think, doesn't even need a libtool.
> A successful build of xearth is e.g.:
> https://redports.org/~mexas/2013071921-42286-133209/xearth-1.2.log
>
> What's going on?

This is a known bug in tinderbox for all environents that use pkgng.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] r326258: 2x depend (depend_package in x11-toolkits/tk84), 2x leftovers, 6x depend (depend_package in devel/t1lib), 13x success, 1x depend (depend_package in devel/xdg-utils)

[Bernhard Fröhlich]

Am 05.09.2013 23:23 schrieb "Boris Samorodov" :
>
> 06.09.2013 00:45, olli hauer пишет:
> > On 2013-09-05 21:45, Ports-QAT wrote:
> >> Add an explicit dependency upon pkg-config (USES+=pkgconfig)
> >> uncovered by an exp libiconv -> inconv swith.
> >>
> >> Approved by: portmgr (implicit)
> >> -
> >>
> >>   Build ID:  20130904075600-2482
> >>   Job owner: b...@freebsd.org
> >>   Buildtime: 36 hours
> >>   Enddate:   Thu, 05 Sep 2013 19:45:04 GMT
> >>
> >>   Revision:  r326258
> >>   Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=326258
> >
> >
> >
> > In tinderbox it looks like this (sample from a view hundred failed ports
> > because of the pkgconf changes without bumping PORTREVISION)
> >
> > pkg_add libxml2-2.8.0_2.txz
> > Installing libxml2-2.8.0_2...missing dependency pkgconf-0.9.3
> > Failed to install the following 1 package(s): libxml2-2.8.0_2.txz
> > error in dependency libxml2-2.8.0_2.txz, exiting
> >
> > To solve the issue bump textproc/libxml2 PORTREVISION and start over
>
> Hm, are you sure it helps? I ask because pkgconf is a build dependency,
> so bumping PORTREVISION has little to no sence.
>
> --
> WBR, Boris Samorodov (bsam)
> FreeBSD Committer, http://www.FreeBSD.org The Power To Serve

I have cleared all cached packages on redports and qat so the problem
should be gone once the backlog has been build.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports.org down?

[Bernhard Fröhlich]

Am 28.09.2013 18:38 schrieb "Fernando Apesteguía" <
fernando.apesteg...@gmail.com>:
>
> Hi all,
>
> redports.org seems to be down.
>
> Any information about when it will be available again?
>
> Thanks!

How did you came to that conclusion? Right now it seems to work fine for me.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADSUP] Staging, packaging and more

[Bernhard Fröhlich]

On Sun, Oct 6, 2013 at 2:20 PM, Ulrich Spörlein  wrote:
> 2013/10/4 Bryan Drewery :
>> On Fri, Oct 04, 2013 at 09:01:58AM +0200, Baptiste Daroussin wrote:
>>> On Fri, Oct 04, 2013 at 08:57:53AM +0200, Erwin Lansing wrote:
>>> > On Fri, Oct 04, 2013 at 08:32:59AM +0200, Baptiste Daroussin wrote:
>>> > > > > > >
>>> > > > > > > Please no devel packages.
>>> > > > > >
>>> > > > > > Seconded.
>>> > > > >
>>> > > > > What's wrong with devel packages?
>>> > > >
>>> > > > It complicates things for developers and custom software on
>>> > > > FreeBSD. The typical situation that I see on most Linux platforms is a
>>> > > > lot of confusion by people, why their custom software XYZ does not
>>> > > > properly build - the most common answer: they forgot to install a
>>> > > > tremendous amount of dev packages, containing headers, build tools and
>>> > > > whatnot.
>>> > > > On FreeBSD, you can rely on the fact that if you installed e.g. libGL,
>>> > > > you can start building your own GL applications without the need to
>>> > > > install several libGL-dev, libX11-dev, ... packages first.
>>> > > > This is something, which I personally see as a big plus of the FreeBSD
>>> > > > ports system and which makes FreeBSD attractive as a development 
>>> > > > platform.
>>> > > >
>>> > >
>>> > > On the other ends, that makes the package fat for embedded systems, 
>>> > > that also
>>> > > makes some arbitrary runtime conflicts between packages (because they 
>>> > > both
>>> > > provide the same symlink on the .so, while we could live with 2 version 
>>> > > at
>>> > > runtime), that leads to tons of potential issue while building locally, 
>>> > > and
>>> > > that makes having sometime insane issues with dependency tracking. Why 
>>> > > having
>>> > > .a, .la, .h etc in production servers? It could greatly reduce PBI 
>>> > > size, etc.
>>> > >
>>> > > Personnaly I do have no strong opinion in one or another direction. 
>>> > > Should we be
>>> > > nicer with developers? with end users? with embedded world? That is the 
>>> > > question
>>> > > to face to decide if -devel packages is where we want to go or not.
>>> > >
>>> >
>>> > If we chose to go down that path, at least we should chose a different
>>> > name as we've used the -devel suffix for many years for developmental
>>> > versions.
>>> >
>>> > I must agree that it is one of the things high on my list of things that
>>> > irritate me with several Linux distributions but I can see the point for
>>> > for embedded systems as well.  But can't we have both?  Create three
>>> > packages, a default full package and split packages of -bin, -lib,
>>> > and even -doc.  My first though twas to make the full package a
>>> > meta-package that would install the split packages in the background,
>>> > but that would probably be confusing for users at the end of the day, so
>>> > rather just have it be a real package.
>>> >
>>> I do like that idea very much, and it is easily doable with stage :)
>>
>> +1 to splitting packages for embedded usage.
>
> -1 for the split, as it will not fix anybody's problem.
>
> On regular machines, disk space is cheap and having to install more
> packages is just annoying to users. Think of the time wasted that
> people are told to apt-get libfoo-dev before they can build anything
> from github, or similar.
>
> If you actually *are* space constricted on your tiny embedded machine,
> what the fuck are you doing with the sqlite database and all the
> metadata about ports/packages anyway? Just rm /usr/include and
> /usr/share/doc, /usr/share/man, etc. when building your disk image.
> But you are doing that already anyway, so this solves no actual
> problem for you.
>
> My two cents
> Uli

I also don't see why we need to optimize our packages for an embedded
environment that is usually very customized. Wouldn't it make more sense to
provide some proper port / packaging options/flags that help to optimize
size of the packages without touching header files? People could use that
flags and poudriere to build their packages together with all their other
compiler flags and cpu optimisations.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: do redports support STAGE yet?

[Bernhard Fröhlich]

Am 09.10.2013 21:19 schrieb "Anton Shterenlikht" :
>
> Do redports.org understand STAGE?
>
> Anton

I did not verify myself but I was told that tinderbox and poudriere should
support staging out of the box. Redports is using tinderbox so yes it
should just work.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 10.0-hosted tinderbox: 8.4 builds broken?

[Bernhard Fröhlich]

Am 09.10.2013 13:10 schrieb "Alexey Dokuchaev" :
>
> Hi there,
>
> I've started to observe the following error when trying to tinderbuild
> (freshly cvs up'ed from marcuscom.com) a port for -b 8.4:
>
>   ...
>   add_pkg pkg-1.1.4_7.tbz
>   adding dependencies
>   pkg_add pkg-1.1.4_7.tbz
>   The package management tool is not yet installed on your system.
>   Do you want to fetch and install it now? [y/N]: tar: Error opening
> archive: Failed to open 'pkg-1.1.4_7.tbz'
>   /buildscript: ./pkg-static: not found
>   error in dependency pkg-1.1.4_7.tbz, exiting
>
> In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are
> different (.txz vs. .tbz).
>
> Why does it happen?  I was under impression that 8.x will never switch to
> pkgng.  Am I doing something wrong, or need to configure my tindy somehow?

I have seen the same on redports today. It did work fine with crees chroot
patch r7 but seems to be broken with what has landed it the ports tree.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports too busy?

[Bernhard Fröhlich]

Am 15.10.2013 14:27 schrieb "Anton Shterenlikht" :
>
> Just to check the reports is running ok.
> I see several ports building for 43 hours.
> Is that expected?
>
> Anton

Yeah that is okay. This is a bug in tinderbox that happens to leave a
/tmp/trinderdlock directory behind when not properly shutdown. So when
starting a new job tinderbox does not start the job and just waits because
it thinks it can't get the lock - I usually see that after some hours and
remove that directory to get it going. I've done this a few hours already
so the jobs should finish soon.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: RFC: USES=kernsrc

[Bernhard Fröhlich]

Am 29.10.2013 16:09 schrieb "René Ladan" :
>
> Hi all,
>
> while stagifying the sysutils/biosfont port together with bapt@ at
> last EuroBSDCon the idea for a USES=kernsrc (or USES=kld ?) came up.
> This new USES would both simplify and unify writing kernel module
> ports because it adds all the common lines.
>
> The result is at http://people.freebsd.org/~rene/patches/kernsrc.mk
> (download it into Mk/uses/ ). An example of a converted port is at
> http://people.freebsd.org/~rene/patches/biosfont.diff
>
> Last nits to solve:
> - decide about MAINTAINER
> - maybe change plist substitution to "${KMODDIR:C,^/,,}" (i.e. strip
> leading '/' )
> - maybe mute ${ECHO_CMD} lines (prefix with '@') in kernsrc-post-install
target
>
> Documentation:
> - add a note to CHANGES
> - add a section to the Porters Handbook

Looks very good to me and I am looling forward to using it for vbox kmod.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

KMODDIR needs to be fixed [was: Re: [QAT] r332657: 4x leftovers]

[Bernhard Fröhlich]

Am 04.11.2013 02:20 schrieb "Ports-QAT" :
>
> Explicitly set KMODDIR to /boot/modules to avoid picking up /boot/kernel
> as KMODDIR from /usr/share/mk/bsd.own.mk included by the distribution
> Makefile.

Yeah I have noticed the same problem with vbox some months ago when I tried
to support overriding KMODDIR. This would be needed by some jails that have
a read only /boot.
I think we should fix this properly now that we have you new USES=kernsrc.
We can either introduce a new variable PORTSKMODDIR or we hack/fix
bsd.own.mk.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] r334619: 1x leftovers, 3x success

[Bernhard Fröhlich]

Am 23.11.2013 01:27 schrieb "Gerald Pfeifer" :
>
> Okay, now I am confused.  How can my workaround work for three quadrants
> of {8.4,9.2} x {amd64,i386} and fail for just one combination?
>
> Gerald
>
> On Sat, 23 Nov 2013, Ports-QAT wrote:
> > Work around ports infrastructure breakage introduced with staging and
> > remove info/gcc46 ourselves.
> >
> > Reported by:  QAT, amdmi3, mandree, bf, dbn
> > PR:   184178
> > -
> >
> >   Build ID:  2013110400-1181
> >   Job owner: ger...@freebsd.org
> >   Buildtime: 2 hours
> >   Enddate:   Sat, 23 Nov 2013 00:19:05 GMT
> >
> >   Revision:  r334619
> >   Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=334619
> >
> > -
> >
> > Port:lang/gcc46 4.6.4_1,1
> >
> >   Buildgroup: 8.4-QAT/amd64
> >   Buildstatus:   SUCCESS
> >   Log:
https://qat.redports.org//~ger...@freebsd.org/2013110400-1181-230452/gcc-4.6.4_1,1.log
> >
> >   Buildgroup: 8.4-QAT/i386
> >   Buildstatus:   SUCCESS
> >   Log:
https://qat.redports.org//~ger...@freebsd.org/2013110400-1181-230453/gcc-4.6.4_1,1.log
> >
> >   Buildgroup: 9.2-QAT/amd64
> >   Buildstatus:   SUCCESS
> >   Log:
https://qat.redports.org//~ger...@freebsd.org/2013110400-1181-230454/gcc-4.6.4_1,1.log
> >
> >   Buildgroup: 9.2-QAT/i386
> >   Buildstatus:   LEFTOVERS
> >   Log:
https://qat.redports.org//~ger...@freebsd.org/2013110400-1181-230455/gcc-4.6.4_1,1.log
> >
> >
> > --
> > Buildarchive URL: <
https://qat.redports.org/buildarchive/2013110400-1181>
> > redports 

Hm definitely a good question. The job defines an exact revision as stated
on top of the mail and this is what the builder checks out and builds.

Revision:  r334619

So no good idea at the moment.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] r334788: 1x depend (depend_package in databases/rrdtool), 3x leftovers

[Bernhard Fröhlich]

Am 25.11.2013 18:30 schrieb "Boris Samorodov" :
>
> (reformatted for consistency sake)
>
> 25.11.2013 18:26, Jason bacon пишет:
> > On 11/25/13 2:56 AM, Boris Samorodov wrote:
> >>
> >> I'm not sure how to deal with /home/$USER leftovers (i.e. while
> >> package install a new user/group is created and while package
> >> deinstalled /home/$USER becomes a leftover, but we display a
> >> message that a user should be removed manually):
> >>
> >> [...]
> >> 
> >> ===>   Building package for slurm-2.6.4
> >> Deleting slurm-2.6.4
> >> Deinstallation has been requested for the following 1 packages:
> >>
> >> slurm-2.6.4
> >>
> >> The deinstallation will free 51 MB
> >> [1/1] Deleting slurm-2.6.4...==>  You should manually remove the
"slurm"
> >> user.
> >>   done
> >> 
> >>
> >> === Checking filesystem state
> >> list of extra files and directories in / (not present before this port
> >> was installed but present after it was deinstalled)
> >>   305288 drwxr-xr-x3 root wheel
> >> 64 Nov 24 20:32 home
> >>   346190 drwxr-xr-x2 slurmslurm
> >>   0 Nov 24 20:32 home/slurm
> >> [...]
> >>
> > The files in /home/$USER (and /var) should be preserved.  Deinstalls may
> > be part of an upgrade process, vs permanent removal, and some of these
> > files contain usage statistics needed by sysadmins for reporting.
> >
> > I would suggest the following deinstall message:
> >
> > "You may remove /home/$USER if you are no longer using SLURM."
>
> Yep, that is the question: why did QAT suggests manuall removing
> _and_ exit with error code?

With my QAT hat on I consider this a false positive. You can safely ignore
that complain from QAT.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 21:04 schrieb "Mike Jakubik" <
mike.jaku...@intertainservices.com>:
>
> Hello,
>
> I've updated to the recent 4.2.20 version only to find a runtime error
due to libstdc++, I see the recent commit made to fix this on 10, however I
am running 9-stable and do not have compat9x installed. I wish thisport did
not need gcc to compile, it always seems to be a problem.

I can only repeat myself. It will not happen any day soon because clang
does not support global register variables and they do not seem to have any
interest to implement that.

> $ VirtualBox
> VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
/usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by
/usr/local/lib/virtualbox/VBoxRT.so not found

Your setup is very strange but it's about the same issue as on 10 as it
seems. With the update to 4.2.20 I have added a change that should add the
gcc path to the ports gcc of libstdc++.so.6 to the vbox rpath but it seems
to have no effect for you.

Could you please send me the following output just to verify:
strings /usr/lib/libstdc++.so.6 | grep GLIBCXX

On my FreeBSD 10 machine there is no such file so I wonder if that might be
a leftover file from a base update.

> $ uname -a
> FreeBSD freebsd.local 9.2-STABLE FreeBSD 9.2-STABLE #0: Wed Dec 11
13:51:20 EST 2013 mjakubik@freebsd.local:/usr/obj/usr/src/sys/FREEBSD  amd64
>
> $ pkg info|grep virtualbox
> virtualbox-ose-4.2.20  A general-purpose full virtualizer for x86
hardware
> virtualbox-ose-kmod-4.2.20 VirtualBox kernel module for FreeBSD
>
> $ pkg info|grep gcc
> gcc-4.6.4  GNU Compiler Collection 4.6
>
> /etc/make.comf
>
> WITH_CLANG_IS_CC=true
> WITHOUT_GCC=true
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 21:42 schrieb "Mike Jakubik" <
mike.jaku...@intertainservices.com>:
>
> On 12/11/13 15:32, Bernhard Fröhlich wrote:
>>
>> I can only repeat myself. It will not happen any day soon because clang
>> does not support global register variables and they do not seem to have
any
>> interest to implement that.
>
>
> Got it.
>
>> Could you please send me the following output just to verify:
>> strings /usr/lib/libstdc++.so.6 | grep GLIBCXX
>>
>> $ strings /usr/lib/libstdc++.so.6 | grep GLIBCX
>
>
> GLIBCXX_3.4
> GLIBCXX_3.4.1
> GLIBCXX_3.4.2
> GLIBCXX_3.4.3
> GLIBCXX_3.4.4
> GLIBCXX_3.4.5
> GLIBCXX_3.4.6
> GLIBCXX_3.4.7
> GLIBCXX_3.4.8
> GLIBCXX_3.4.9
> GLIBCXX_FORCE_NEW
>
> make delete-old and delete-old-libs does not remove anything from my
system at this point, i am going to try compile again but with gcc47 this
time.
>
> Thanks!

That definitely is the libstdc++ from our ancient gcc 4.2 in base. Could
you try to temporary rename the so and try to start vbix again? Don't
forget to rename it afterwards if there are any binaries that still need it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 22:16 schrieb "Mike Jakubik" <
mike.jaku...@intertainservices.com>:
>
> On 12/11/13 15:51, Bernhard Fröhlich wrote:
>>
>>
>> That definitely is the libstdc++ from our ancient gcc 4.2 in base. Could
you try to temporary rename the so and try to start vbix again? Don't
forget to rename it afterwards if there are any binaries that still need it.
>>
>
> Renaming /usr/lib/libstdc++.so.6 addresses the problem. Do you know a way
to check if anything else might need this?
>
> Thank you.

You could either try manually with ldd which so a binary needs or I think
bsdadmin scrips contains some libcheck script that can check that in bulk.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

[Bernhard Fröhlich]

Am 22.12.2013 12:13 schrieb "José García Juanino" :
>
> Hello,
>
> I have running a recent FreeBSD 10.0-RC2, and I get the following
scenario:
>
> www/opera depends on lang/gcc46
> devel/kBuild depends on lang/gcc
>
> But both gcc46 and gcc are incompatible, so I cannot install opera and
> kBuild. However, lang/gcc and lang/gcc46 install the same versión compiler
> 4.6.4. Any idea to fix this conflict? I am using  pkgng to install the
> ports.

kBuild is using USE_GCC=yes which uses lang/gcc right now in version 4.6.

Opera has a strict dependency on on FreeBSD 10 for gcc4.6 because of
libstdc++.so.6.

RUN_DEPENDS+=   ${LOCALBASE}/lib/gcc46/libstdc++.so.6:${PORTSDIR}/lang/gcc46

I am not sure if opera really needs to be that strict on which libstdc++ it
uses since it also seems to be happy with libstdc++ from gcc 4.2 on FreeBSD
9.

I've cc'd the opera maintainer so let's see what he thinks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

[Bernhard Fröhlich]

Am 22.12.2013 21:57 schrieb "Dirk Meyer" :
>
> Bernhard Fröhlich schrieb:,
>
> > Am 22.12.2013 12:13 schrieb "Jos=E9 Garc=EDa Juanino" <
jjuan...@gmail.com>:
> > > I have running a recent FreeBSD 10.0-RC2, and I get the following
> > scenario:
> > >
> > > www/opera depends on lang/gcc46
> > > devel/kBuild depends on lang/gcc
> > >
> > > But both gcc46 and gcc are incompatible, so I cannot install opera and
> > > kBuild. However, lang/gcc and lang/gcc46 install the same versi=F3n
compi=
> > ler
> > > 4.6.4. Any idea to fix this conflict? I am using  pkgng to install the
> > > ports.
> >
> > kBuild is using USE_GCC=3Dyes which uses lang/gcc right now in version
4.6.
> >
> > Opera has a strict dependency on on FreeBSD 10 for gcc4.6 because of
> > libstdc++.so.6.
>
> In C++ you can not reuse your libraries without recompilation.
> This breaks the goal of object oriented design as stated in several books.

Why does opera work fine with libstdc++ from gcc 4.2 then?

> Opera has an option to pick your poison.
> you can set COMPAT9, which does conflict with virtualbox.

No it does not conflict anymore. That has been fixed already.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

[Bernhard Fröhlich]

Am 23.12.2013 11:10 schrieb "José García Juanino" :
>
> On 23 December 2013 08:36, Bernhard Fröhlich  wrote:
> >
> > Am 22.12.2013 21:57 schrieb "Dirk Meyer" :
> > > Opera has an option to pick your poison.
> > > you can set COMPAT9, which does conflict with virtualbox.
> >
> > No it does not conflict anymore. That has been fixed already.
>
> Only a remark: the goal is install emulators/virtualbox-ose-additions and
www/opera on a
> VirtualBox FreeBSD 10.0RC2. I have found a workaround:
>
> 1- First,  install emulators/virtualbox-ose-additions  with pkgng. Then
you will get /usr/local/lib/gcc46/libstdc++.so.6
> installed by lang/gcc port.
> 2- Install www/opera from ports: cd /usr/ports/www/opera && make install
clean. This trick  works as the port only
> check the installation of the libstdc++.so.6; it does not care the which
package installed the library.
>
> Yes, there are some corner cases you need the flexibility of the port
system :-)
>
> Best regards

Yeah, that should work fine and my proposal was to change opera to depend
on lang/gcc instead of lang/gcc46 because it is what most ports will use on
FreeBSD 10.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Updating openjdk6-b29 makes my system freeze and reboot

[Bernhard Fröhlich]

Am 08.01.2014 19:00 schrieb "Leslie Jensen" :
>
>
> openjdk6-b29  <   needs updating (index has b28_7,1)
>
>
> When running portmaster -a my system freezes after a while and reboots.
>
> I don't know how to get past this.
>
> Any suggestions

The b29 update is triggering a serious bug in the kernel that causes this
issues. You can either update to a very recent FreeBSD stable (maximum
about a week old) or you can (forcibly) deinstall openjdk6 and install it
again which will use the bootstrapping jdk. Updating to b28 by using b29 to
compile it will not work.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]

[Bernhard Fröhlich]

Am 11.01.2014 03:49 schrieb "Craig Rodrigues" :
>
> Hi,
>
> I had problems with the virtualbox-ose-4.22 port
> under FreeBSD 10.0-RC5, where VirtualBox would occasionally
> crash.
> It looks like the mix of QT C++ libraries compiled with clang,
> vs. the virtualbox-ose port compiled with g++46 was not a good mix

I still think that this is a problem that needs to be fixed in Qt or even
better in our ports tree. The decision to compile parts of the portstree
with the base compiler and other parts with various compilers from ports is
what causes all this issues. Hacking virtualbox cures the symptoms but does
not fix the cause.

> After reading this post:
>
http://lists.freebsd.org/pipermail/freebsd-emulation/2013-December/011171.html
>
> I obtained Jung-uk Kim's port Makefiles for VirtualBox and
> I managed to compile a build of VirtualBox 4.3.6 on my system which is not
> crashing.
>
> This is what I did:
>
> (1)   Delete the virtualbox-ose port from my system:
>
> pkg delete virtualbox-ose
> pkg delete virtualbox-ose-kmod
>
> (2)   Delete the gsoap port from my system
>
> pkg delete gsoap
>
> (3)  Make sure that a valid FreeBSD src tree exists under /usr/src,
otherwise
>   the build will fail.
>
> (4)  Check out jkim's tree from redports:
>
> mkdir -p /tmp/xy
> cd /tmp/xy
> svn co https://svn.redports.org/jkim
>
> (5)   Build and install gsoap from jkim's port (you need to do this
because the version of gsoap in the ports tree will result in failed
compilation):
>
> cd /tmp/xy/jkim/devel/gsoap
> make
> make install

Really? From what I was told the current gsoap should work fine with the
patch that he included for the new gsoap in his tree.

> (6)  Build and install virtualbox-ose and virtualbox-ose-kmod ports.
>
> cd /tmp/xy/jkim/emulators/virtualbox-ose
> make
> make install
> cd /tmp/xy/jkim/emulators/virtualbox-ose-kmod
> make
> make install

That is the wrong order. You need to install kmod first or virtualbox will
pull in kmod from the portstree in /usr/ports.

> After doing this, I got a build of VirtualBox that:
> -> built against clang, does not depend on g++ libraries
> -> no need to unset QT_PLUGIN_PATH
> -> works and doesn't crash :)
>
> Thank you for doing this Jung-uk, it was quite a lot of work
> to port VirtualBox to clang!

I still think this is the wrong approach and I won't maintain all those
clang patches in the official port. The problem that I see is that we are
diverging from upstream vbox too much and end up maintaining a very special
usecase and a few dozen patches on our own. We would be the only one to
build with clang so with every release we need to update our patches and
add more to keep it building with clang. This will need someone that want's
to do it for the next few years.

Since the beginning of vbox on FreeBSD we tried to stay close to upstream
sources and push patches to upstream first. This has worked good for us and
has created a good relationship to them.

So we have 3 options:

- I step down and wish you all the best. There are a few smart people
working on vbox now so it should not be an issue for the project.

- Someone clones the vbox ports and maintains the clang version in the
portstree.

- We try to push as many patches upstream and nag them until they accept
them. This might also interest some Mac OS X people.

I will talk to the vbox developers to find out what they think of clang and
if someone is working on updating the recompiler from qemu which would make
a full clang build possible.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36

[Bernhard Fröhlich]

Am 05.03.2016 1:01 vorm. schrieb "Michael" :
>
> Hi all,
>
>
>
> I write this as I like to request a major upgrade for virtualbox related
> ports on freebsd.
>
>
>
> Currently I face problems using the current ports with php70 port
compiled.
>
> I don't want to go back to port php56.
>
>
>
> Those problems can easy be fixed when phpvirtualbox-4.3.2 gets an upgrade
to
> phpvirtualbox-5.0-5
>
> as it now support php7 out of the box.
>
> Please have a look:
> https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt
> Changelog.
>
> But before upgrading, the new Virtualbox version must be upgraded also see
> https://www.virtualbox.org/wiki/Downloads
>
>
>
> Please can those ports be upgraded by someone for support of systems
running
> PHP 7?
>
>
>
> Category www
>
> 
>
>
>
> phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
>
>
> Category emulators
>
> --
>
>
>
> virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
> virtualbox-ose-additions-4.3.36  needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
> virtualbox-ose-kmod-4.3.36  needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
>
>
>
>
> Thank you for all the work!
>
>
>
> With best regards,
>
> Michael

Hi Michael,

we know that we need to update vbox to 5.x but the sad truth is that we do
not have a reasonable stable version of it. The port builds but the kernel
module doesn't work properly so instead of breaking vbox for all people we
will just stay at the last stable version that we have. phpvirtualbox is
not backwards compatible so you have two options:

1) help on vbox 5.x port
2) create a phpvirtualbox patch for php7
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: mythtv-0.27.5.20150616

[Bernhard Fröhlich]

I did not have time yet to look into it. I was working on a mythtv 0.27.6 update
which I want to finish before I start with 0.28.

Right now I am bit upset by the policy that the mythtv guys seem to have. They
are doing patch releases without fixing critical CVEs. The 0.27.6 release is a
good example because it contains a lot of old ffmpeg security issues which have
not been fixed.


On Tue, Apr 19, 2016 at 3:57 PM, HILLIARD, Craig
 wrote:
> Do you have estimated timing when MythTV 0.28 will be available in ports?
>
> thanks
>
> Craig Hilliard
> IT Support Technician
> Auto Inergy Division
> Direct: 864-622-2470  Mobile: 864-844-3489
> craig.hilli...@plasticomnium.com
>
>
>
> This message and all attachments are highly confidential and intended solely
> for the addressees.
> Any use not in accord with its authorised purpose, any dissemination or
> disclosure, either whole or partial, is prohibited except if it has been
> expressly authorised through a written confidentiality agreement or through
> a written approval by its sender or by the legal representative of Plastic
> Omnium Gestion, SNC.
> If you receive this message in error, please delete it and immediately
> notify the sender.
> Neither Plastic Omnium Gestion, SNC, nor any of its affiliated companies of
> the Plastic Omnium Group shall be liable for the content of the message and
> its attachment(s), notably but not limitative if it has been altered,
> changed or falsified.
>
>
>
>  Please do not print this email unless necessary.



-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: amule 2.2.3 port - first try

[Bernhard Fröhlich]

On Tue, December 30, 2008 7:04 pm, Torfinn Ingolfsen wrote:
> Hello,
>
> On Tue, Dec 30, 2008 at 11:20 AM, Bernhard Froehlich 
> wrote:
>> Looks like you are in the wrong folder. Patches are relative to the
>> WRKSRC
>> directory. (work/aMule-2.2.3 or something like that) So recreate the
>> patch from
>> within that directory and it should work.
>
> I'm not really sure what you are saying here? The patch I provide is
> fr the port itself (ie the 'amule2' directory in /usr/ports/net-p2p).
> It is best applied from withing the amule2 directory, uing patch -p1 ...
> Or did you find some other problem with the patch? If so, it would
> help if you could be more specific about the error(s).
>
>> I've had a quick look over your patch and it seems to miss a few files.
>> Have a
>
> Could you be more specific?
>

Sorry that was my fault. I thought you wanted to delete a file from within
the aMule sourcecode and not one of the port files. That makes a lot more
sense now.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for testers: MythTV 0.21 port upgrade

[Bernhard Fröhlich]

On Thu, January 15, 2009 11:35 pm, Greg Larkin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Greg Larkin wrote:
>> Mark Linimon wrote:
>>> On Wed, Dec 31, 2008 at 04:57:58PM +, Craig Butler wrote:
>>>> Any updates on the 0.21 version of Mythtv ??  I see that we are still
>>>> at
>>>> 0.20 in ports
>>> If there's progress on 0.21, someone needs to say so -- the 0.20
>>> version is already past its deletion date since it has been broken
>>> for so long.  I'll make the commit to change the date if there is.
>>
>>> mcl
>>
>> Hi all,
>>
>> I am currently working on the following MythTV-related PRs and plan to
>> close them soon:
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127856
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127857
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419
>>
>> Please don't delete multimedia/mythtv yet.  The last PR above contains a
>> patch to upgrade it to 0.21.
>>
>> Regards,
>> Greg
>
> Hello all of you MythTV supporters with the collective patience of the
> universe!
>
> I recently committed mythtv-frontend (PR 127856) and mythtv-themes (PR
> 127857), and please let me know if you see any problems with the updates.
>
> There is still some work to be done on multimedia/mythtv, and I'm
> tackling that next.
>
> Thanks again for your patience and feedback!
>

Yiiha, great to hear that :o) I will update and test as soon as time permits.

Do you plan to update multimedia/mythtv to 0.21 or just fix it and leave
it at 0.20? Because in the later case there is at least one open compile
problem from Torfinn Ingolfsen that hasn't been tackled down yet.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: amule 2.2.3 port - ready for test

[Bernhard Fröhlich]

On Sun, January 18, 2009 1:05 pm, Torfinn Ingolfsen wrote:
> Hello,
>
> On Mon, Jan 12, 2009 at 9:46 AM, Bernhard Fröhlich 
> wrote:
>> On Sat, January 10, 2009 5:28 pm, Torfinn Ingolfsen wrote:
>>> Hello,
>>>
>>> On Sat, Jan 10, 2009 at 4:20 PM, Bernhard Froehlich 
>>> wrote:
>>>> I've applied your patch and compiled the port in an i386 Tinderbox for
>>>> 6-STABLE and 7-STABLE. It compiles fine but leaves a few files behind
>>>> and deletes a few directories which it shouldn't.
>>>
>>> Thanks for testing. A new patch will be sent to the mailing list.
>>> I really must get my own tinderbox running again soon.
>>
>> I've build your -5 patch and tinderbox keeps complaining about some
>> missing directories.
>
> I'm still having problems getting my own tinderbox to run. Maybe I
> should just reinstall it (it was upgraded).
>
> amule - I wonder why 'port test' doesn't complain about missing files
> like your tinderbox does?

To be exact tinderbox complains about some directories that you have
removed but you shouldn't. So just remove these lines from pkg-plist and
tinderbox should be happy with it.

portlint and port-tools are great tools for a quick check but a tinderbox
can detect a lot more errors because it builds the ports in a clean
environment so none of them can replace one another. Use them in
combination and you catch most of the errors.

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for testers: MythTV 0.21 port upgrade

[Bernhard Fröhlich]

On Fri, January 23, 2009 2:36 am, Greg Larkin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bernhard Fröhlich wrote:
>> On Thu, January 15, 2009 11:35 pm, Greg Larkin wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Greg Larkin wrote:
>>>> Mark Linimon wrote:
>>>>> On Wed, Dec 31, 2008 at 04:57:58PM +, Craig Butler wrote:
>>>>>> Any updates on the 0.21 version of Mythtv ??  I see that we are
>>>>>> still
>>>>>> at
>>>>>> 0.20 in ports
>>>>> If there's progress on 0.21, someone needs to say so -- the 0.20
>>>>> version is already past its deletion date since it has been broken
>>>>> for so long.  I'll make the commit to change the date if there is.
>>>>> mcl
>>>> Hi all,
>>>>
>>>> I am currently working on the following MythTV-related PRs and plan to
>>>> close them soon:
>>>>
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127856
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127857
>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419
>>>>
>>>> Please don't delete multimedia/mythtv yet.  The last PR above contains
>>>> a
>>>> patch to upgrade it to 0.21.
>>>>
>>>> Regards,
>>>> Greg
>>> Hello all of you MythTV supporters with the collective patience of the
>>> universe!
>>>
>>> I recently committed mythtv-frontend (PR 127856) and mythtv-themes (PR
>>> 127857), and please let me know if you see any problems with the
>>> updates.
>>>
>>> There is still some work to be done on multimedia/mythtv, and I'm
>>> tackling that next.
>>>
>>> Thanks again for your patience and feedback!
>>>
>>
>> Yiiha, great to hear that :o) I will update and test as soon as time
>> permits.
>>
>> Do you plan to update multimedia/mythtv to 0.21 or just fix it and leave
>> it at 0.20? Because in the later case there is at least one open compile
>> problem from Torfinn Ingolfsen that hasn't been tackled down yet.
>>
>
> Hi Bernhard,
>
> I do plan to update multimedia/mythtv to 0.21, if at possible.  This PR
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419) is a patch to
> update 0.20, but is that the one that you're saying still has a compile
> problem?

That is good news and probably the better way to go. Yes that compile
problem occured with that patch but was specific to 0.20 so you can forget
about it and just move on.


-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: amule 2.2.3 port - ready for test

[Bernhard Fröhlich]

On Thu, February 26, 2009 12:22 am, Torfinn Ingolfsen wrote:
> Hello,
>
> On Wed, Feb 25, 2009 at 2:08 PM, Bernhard Fröhlich 
> wrote:
>> I've tried to build it in my tinderbox and it looks like the ftp/curl
>> dependency is specified incorrect. Build log is attached.
>
> Aha, I hadn't updated the ports tree in my Tinderbox. Sorry about that.
> The attached version should work better.

Builds fine for me :o)

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for testers: MythTV 0.21 port upgrade

[Bernhard Fröhlich]

On Tue, March 10, 2009 10:43 pm, Greg Larkin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bernhard Fröhlich wrote:
>> On Fri, January 23, 2009 2:36 am, Greg Larkin wrote:
>>> -BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Bernhard Fröhlich wrote:
>>>> On Thu, January 15, 2009 11:35 pm, Greg Larkin wrote:
>>>>> -BEGIN PGP SIGNED MESSAGE-
>>>>> Hash: SHA1
>>>>>
>>>>> Greg Larkin wrote:
>>>>>> Mark Linimon wrote:
>>>>>>> On Wed, Dec 31, 2008 at 04:57:58PM +, Craig Butler wrote:
>>>>>>>> Any updates on the 0.21 version of Mythtv ??  I see that we are
>>>>>>>> still
>>>>>>>> at
>>>>>>>> 0.20 in ports
>>>>>>> If there's progress on 0.21, someone needs to say so -- the 0.20
>>>>>>> version is already past its deletion date since it has been broken
>>>>>>> for so long.  I'll make the commit to change the date if there is.
>>>>>>> mcl
>>>>>> Hi all,
>>>>>>
>>>>>> I am currently working on the following MythTV-related PRs and plan
>>>>>> to
>>>>>> close them soon:
>>>>>>
>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343
>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127856
>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127857
>>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419
>>>>>>
>>>>>> Please don't delete multimedia/mythtv yet.  The last PR above
>>>>>> contains
>>>>>> a
>>>>>> patch to upgrade it to 0.21.
>>>>>>
>>>>>> Regards,
>>>>>> Greg
>>>>> Hello all of you MythTV supporters with the collective patience of
>>>>> the
>>>>> universe!
>>>>>
>>>>> I recently committed mythtv-frontend (PR 127856) and mythtv-themes
>>>>> (PR
>>>>> 127857), and please let me know if you see any problems with the
>>>>> updates.
>>>>>
>>>>> There is still some work to be done on multimedia/mythtv, and I'm
>>>>> tackling that next.
>>>>>
>>>>> Thanks again for your patience and feedback!
>>>>>
>>>> Yiiha, great to hear that :o) I will update and test as soon as time
>>>> permits.
>>>>
>>>> Do you plan to update multimedia/mythtv to 0.21 or just fix it and
>>>> leave
>>>> it at 0.20? Because in the later case there is at least one open
>>>> compile
>>>> problem from Torfinn Ingolfsen that hasn't been tackled down yet.
>>>>
>>> Hi Bernhard,
>>>
>>> I do plan to update multimedia/mythtv to 0.21, if at possible.  This PR
>>> (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419) is a patch to
>>> update 0.20, but is that the one that you're saying still has a compile
>>> problem?
>>
>> That is good news and probably the better way to go. Yes that compile
>> problem occured with that patch but was specific to 0.20 so you can
>> forget
>> about it and just move on.
>>
>>
>
> Hi everyone,
>
> I just want to let you know that I've recently committed the MythTV 0.21
> update to the ports tree: http://www.freshports.org/multimedia/mythtv/
>
> Thanks for everyone's help along the way, and let me know if you into
> any problems with the new version of the application.
>

Great work and thanks to all of you! I've just seen the pkg-descr file and
the middle paragraph is now outdated i think ...

>The current distributed version of MythTV
>(http://www.mythtv.org/modules.php?name=Downloads&d_op=viewdownload&cid=1)
>is out of date for just about all platforms.  It is also protocol
>incompatible with the "bug fix" version, which is maintained under
>subversion, rather like the FreeBSD -STABLE branch.  This port is a
>snapshot of svn version 13053, dated 15 March 2007.  Later versions of
>this tree are no longer compatible with this port.


-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mythtv 0.21 - trouble compiling the port

[Bernhard Fröhlich]

DPATH += ../libavcodec ../libavutil
-DEPENDPATH += ../ ../libmythui
-DEPENDPATH += ../libmythupnp
+INCLUDEPATH = ../libmythsamplerate ../libmythsoundtouch
../libmythfreesurround $${INCLUDEPATH}
+INCLUDEPATH = ../libavcodec ../libavutil $${INCLUDEPATH}
+INCLUDEPATH = ../.. ../ ./ $${INCLUDEPATH}
+DEPENDPATH = ../libmythsamplerate ../libmythsoundtouch $${DEPENDPATH}
+DEPENDPATH = ../libmythfreesurround $${DEPENDPATH}
+DEPENDPATH = ../libavcodec ../libavutil $${DEPENDPATH}
+DEPENDPATH = ../ ../libmythui $${DEPENDPATH}
+DEPENDPATH = ../libmythupnp $${DEPENDPATH}


 LIBS += -L../libmythsamplerate   -lmythsamplerate-$${LIBVERSION}



-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mythtv 0.21 - trouble compiling the port

[Bernhard Fröhlich]

On Mon, April 13, 2009 9:22 am, Torfinn Ingolfsen wrote:
> Hello,
>
> 2009/4/12 Greg Larkin :
>> Hi Bernhard,
>>
>> Thank you for preparing that patch.  I am testing it now on my machine
>> here, and I will commit the change once verified.
>>
>> Can anyone else that has had compile errors on this OS/arch combination
>> verify that Bernhard's patch has solved the compile problem?
>
> A small correction here: Bernhard's patch solves *one* compile
> problem, there are still one (or more) compilation problem(s) after
> applying his patch. Please see the other messages in this thread.


Yes, that is correct. It took me some time to figure out why that only
affects multimedia/mythtv and not the multimedia/mythtv-frontend port
though they are nearly the same. The reason is that the mythtranscode
patch got lost on the way because it was included in my PR but is not in
the repository. So i have reattached it now.

It is nearly useless to test them in a tinderbox because the problems are
all conflicts with an installed ffmpeg and that does not happen in a
tinderbox build.

Here are the patches that i've needed to get both ports working again.


multimedia/mythtv:

http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro
http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro


multimedia/mythtv-frontend:

http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro


The good news is, that i've talked to the mythtv developers yesterday and
they have already fixed the include path problems that we regularly
stumble across. So that should not happen again with mythtv 0.22

Thanks to the testers!

-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mythtv 0.21 - trouble compiling the port

[Bernhard Fröhlich]

On Mon, April 13, 2009 8:34 pm, Torfinn Ingolfsen wrote:
> Hello,
>
> 2009/4/13 Bernhard Fröhlich :
>> Here are the patches that i've needed to get both ports working again.
>>
>>
>> multimedia/mythtv:
>>
>> http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro
>> http://home.bluelife.at/ports/mythtv/patch-programs-mythtranscode-mythtranscode.pro
>
> On a freshly updated ports tree and with those two patches, I still
> get this error:
> g++ -c -pipe -march=k8 -fomit-frame-pointer -O3 -g -Wall -Wno-switch
> -Wpointer-arith -Wredundant-decls -Wno-non-virtual-dtor
> -D__STDC_CONSTANT_MACROS -I/usr/local/include/artsc -D_REENTRANT
> [snip]

Looks like another missing patch. Now i've double checked with your list
and this is the last missing one. (also taken from mythtv-frontend)

http://home.bluelife.at/ports/mythtv/patch-libs-libmythtv-libmythtv.pro


>> multimedia/mythtv-frontend:
>>
>> http://home.bluelife.at/ports/mythtv/patch-libs-libmyth-libmyth.pro
>
> But 'make' in mythtv-frontend works with this patch (completes without
> errors), on the same machine.

Jiha :o)


-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mythtv 0.21 - trouble compiling the port

[Bernhard Fröhlich]

On Thu, April 23, 2009 4:14 am, Greg Larkin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bernhard Fröhlich wrote:
> [...]
>>
>> Yes, that is correct. It took me some time to figure out why that only
>> affects multimedia/mythtv and not the multimedia/mythtv-frontend port
>> though they are nearly the same. The reason is that the mythtranscode
>> patch got lost on the way because it was included in my PR but is not in
>> the repository. So i have reattached it now.
>>
>> It is nearly useless to test them in a tinderbox because the problems
>> are
>> all conflicts with an installed ffmpeg and that does not happen in a
>> tinderbox build.
>
> Hi Bernhard,
>
> I have a prepared commits for mythtv and mythtv-frontend and am doing a
> Tinderbox build just to make sure there aren't any silly errors present.
>
> Since you mentioned that ffmpeg has caused conflicts previously, can you
> tell me how to configure and install it so I can run a separate mythtv
> compilation to make sure the patches I have are correct?

Just installing the multimedia/ffmpeg port without any enabled options is
enough. Then build mythtv with ARTS. The problem is that mythtv includes
files from /usr/local/include/libavcodec if it is present but it should
never do that because it has his own ffmpeg version included in his source
and really wants to build with that.

The bug that leads to this is that they use -I../libavcodec as part of
their include path whenever they need their ffmpeg headers and put it at
the end of the include path. But it happens that configure has already put
-I/usr/local/include/arts to the include path and
-I/usr/local/include/arts + -I../libavcodec =
/usr/local/include/arts/../libavcodec which results in including the
system ffmpeg headers - which is wrong, not supported and fails in many
strange ways.

A simple fix is to put -I../libavcodec at the beginning of the include
path then the compiler finds myhttv's ffmpeg headers first and everything
works as expected.

That errors probably never came up because it only fails when the system
ffmpeg headers and the included from mythtv are different in an
incompatible way. It is possible that there are more of that wrong include
paths that haven't been patched yet but i haven't tested it yet. The
easiest check would be to install multimedia/ffmpeg and corrupt each
header file of it by adding "#error GOT YOU" at the beginning or something
else that needs the compiler to give up and raise an error whenever it
happens to include one of the system ffmpeg headers. Then build mythtv
with ARTS support and cross your fingers.


-- 
Bernhard Fröhlich
http://www.bluelife.at/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: redports and build status

[Bernhard Fröhlich]

On Tue, Aug 12, 2014 at 8:54 PM, Tijl Coosemans  wrote:
> On Tue, 12 Aug 2014 19:38:27 +0200 Fernando Apesteguía wrote:
>> Hi there,
>>
>> I built a port in redports and I received a mail notifying that the
>> builds were finished, but it seems redports couldn't figure out if the
>> builds finished successfully.
>>
>> https://redports.org/buildarchive/20140812170901-30860
>>
>>
>> Any ideas of why this happened?
>>
>> Thanks in advance.
>
> I'm seeing a lot of these as well. CCing decke@

Yeah, the "finished" state is some rescue state in case something went
terribly wrong. Usually this happens when something inside redports fails
or some backend behaves very weird or if the port creates some very strange
situation like a recursive dependency (which fills up a temporary partition and
then fails).

If only one of many jobs fails then chances are good that it is some redports
weirdness. If many jobs fail (like in this case) and it is reproducible then the
chances are good that your port is doing something very very bad.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Redports, broken regression tests and missing check-orphans

[Bernhard Fröhlich]

Am 13.08.2014 12:10 schrieb "Vitaly Magerya" :
>
> Bernhard, while we're at it, there are currently two problems with
redports which diminish it's usefulness significantly:
>
> 1. Redports used to run "make regression-test" on every build; right now,
each log has this instead:
>
> 
> [: -eq: unexpected operator
> === Regression tests skipped. ===
> 
>
> So, no regression tests are executed. I don't know what the problem is
here.
>
> 2. Most ports now have stage support; this means that checking for
leftover files under ${PREFIX} is close to useless: only files in pkg-plist
are copied there. Instead, leftovers should be searched for in ${STAGEDIR}
-- running "make stage-qa" and "make check-orphans" with every build would
do that.
>
> (I've already botched two patches when I assumed that successful redports
run means that pkg-plist is complete).
>
> So, can the first problem be fixed and the second suggestion implemented?
Should I be bothering tinderbox author(s) instead?

I am not sure where the first issue is coming from but the second is
definitely a tinderbox task. We are asking for tinderbox staging and modern
leftover checks for some time already. I am working on a poudriere
migration but it's quite a moving target and it requires quite a bit of
work.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] QAT malfunctioning?

[Bernhard Fröhlich]

Am 28.08.2014 18:44 schrieb "Matthias Andree" :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 28.08.2014 um 14:40 schrieb Pietro Cerutti:
> > On 2014-Aug-28, 10:50, Ports-QAT wrote:
> >>   Build ID:  20140828103800-58454
> >>   Job owner: g...@freebsd.org
> >>   Buildtime: 13 minutes
> >>   Enddate:   Thu, 28 Aug 2014 10:50:56 GMT
> >>
> >>   Revision:  366390
> >>   Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=366390
> >>
> >> -
> >>
> >> Port:lang/seed7 05.20140817
> >>
> >>   Buildgroup: 8.4-QAT/amd64
> >>   Buildstatus:   FAIL
> >>
> >>   Buildgroup: 8.4-QAT/i386
> >>   Buildstatus:   SUCCESS
> >>   Log:
https://qat.redports.org//~g...@freebsd.org/20140828103800-58454-404655/seed7-05.20140817.log
> >>
> >>   Buildgroup: 9.2-QAT/amd64
> >>   Buildstatus:   FAIL
> >>
> >>   Buildgroup: 9.2-QAT/i386
> >>   Buildstatus:   FAIL
> >
> > It would really be useful to have the logs for the failed builds,
> > instead of the successful ones..
> >
>
> It appears that it needs some love in general... it's failing for many
> of the commits without logs, so this looks more like a system issue.
> It would be good if someone could tame this.

I'm sorry but it seems that something went badly wrong yesterday after some
maintenance on the builders. I have disabled them yesterday but someone
obviously did reenable them today which caused another flood of wrong QAT
mails. Sorry for all that spam! I will have a look at what is failing as
soon as possible.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] 367736: 4x fail

[Bernhard Fröhlich]

Am 09.09.2014 17:07 schrieb "Sunpoet Po-Chuan Hsieh" :
>
> On Tue, Sep 9, 2014 at 10:48 PM, Ports-QAT  wrote:
>>
>> - Update to 0.005
>>
>> Changes:http://search.cpan.org/dist/Return-Type/Changes
>> -
>>
>>   Build ID:  20140909144400-60289
>>   Job owner: sunp...@freebsd.org
>>   Buildtime: 5 minutes
>>   Enddate:   Tue, 09 Sep 2014 14:48:32 GMT
>>
>>   Revision:  367736
>>   Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=367736
>>
>> -
>>
>> Port:devel/p5-Return-Type 0.005
>>
>>   Buildgroup: 8.4-QAT/amd64
>>   Buildstatus:   FAIL
>>
>>   Buildgroup: 8.4-QAT/i386
>>   Buildstatus:   FAIL
>>
>>   Buildgroup: 9.2-QAT/amd64
>>   Buildstatus:   FAIL
>>
>>   Buildgroup: 9.2-QAT/i386
>>   Buildstatus:   FAIL
>>
>>
>> --
>> Buildarchive URL: <
https://qat.redports.org/buildarchive/20140909144400-60289>
>> redports 
>
>
> I did not find build logs on
https://qat.redports.org/buildarchive/20140909144400-60289
> Where can I get the logs of failed builds to investigate the problem?
> Thanks.
>
> Regards,
> sunpoet

This kind of failure does not create any buildlogs. It happens when an
internal error on QAT happens or some serious dependency issue like
circular dependencies or non existing dependency.

So I would recommend to ignore that mail right now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [QAT] 367734: 4x fail

[Bernhard Fröhlich]

Am 09.09.2014 17:11 schrieb "Philippe Audéoud" :
>
> On Tue, 09 Sep 2014, Ports-QAT wrote:
>
> > - Update to 0.21
> > -
> >
> >   Build ID:  20140909135600-50484
> >   Job owner: jada...@freebsd.org
> >   Buildtime: 3 minutes
> >   Enddate:   Tue, 09 Sep 2014 13:58:35 GMT
> >
> >   Revision:  367734
> >   Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=367734
> >
> > -
> >
> > Port:mail/p5-Mail-GnuPG 0.21
> >
> >   Buildgroup: 8.4-QAT/amd64
> >   Buildstatus:   FAIL
> >
> >   Buildgroup: 8.4-QAT/i386
> >   Buildstatus:   FAIL
> >
> >   Buildgroup: 9.2-QAT/amd64
> >   Buildstatus:   FAIL
> >
> >   Buildgroup: 9.2-QAT/i386
> >   Buildstatus:   FAIL
> >
> >
> > --
> > Buildarchive URL: <
https://qat.redports.org/buildarchive/20140909135600-50484>
> > redports 
>
> Hello,
>
> Like sunpoet@, i don't find any logs in
> https://qat.redports.org/buildarchive/20140909135600-50484 and for the
> moment i can't reproduce reported failure on my 9.2 poudriere.
>
> Regards,
>
> --
> Philippe Audéoud

I am not sure what happened on the build boxes that caused those 2 builds
to fail but I would suggest to ignore the mails right now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Is redports.org back?

[Bernhard Fröhlich]

Am 22.04.2016 17:50 schrieb "Fernando Apesteguía" <
fernando.apesteg...@gmail.com>:
>
> On Fri, Apr 22, 2016 at 5:49 PM, Kurt Jaeger  wrote:
> > Hi!
> >
> >> I noticed that there is an apparently functional redports.org site
> >> again. Is it functional?
> >
> > Interesting find, thanks! No, it does not look yet functional.
>
> Damn it! I was starting to cry of happiness. I hope it's back soon :)
>
> >
> >> All I get is a "No authenticated" message when I try to log in.

We're not there yet. There is still some work to do. Code can be found on
github.

http://github.com/freebsd/redports
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Is redports.org back?

[Bernhard Fröhlich]

Am 22.04.2016 22:21 schrieb "Mathieu Arnold" :
>
>
>
> +--On 22 avril 2016 17:43:07 +0200 Fernando Apesteguía
>  wrote:
> | Hi,
> |
> | I noticed that there is an apparently functional redports.org site
> | again. Is it functional? All I get is a "No authenticated" message
> | when I try to log in.
>
> It looks like there is a front-end, yes, but it's going to lack backend
> builders, they were repurposed months ago.

The most important point is to finish the code. Once that I have a working
prototype we can start to think about a production system. Automating tasks
like builder updates, hardware, people that keep the service running and
probably some political topics.

If it works out fine we might get hardware from portmgr or the foundation
(with some politics involved) if not I can still try to run the backends in
the cloud.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: emulators/virtualbox-ose build failure

[Bernhard Fröhlich]

On Mon, Aug 1, 2016 at 1:47 PM, Matthias Petermann (Business)
 wrote:
> Hello,
>
> during the last build of my custom package repository I did experience a
> strange issue. I am using Synth, the build host is running FreeBSD
> 10.3/amd64. For the last build run, I receive an error:
>
> In file included from
> /construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/cpu-exec.c:30:
> /construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/target-i386/exec.h:41:30:
> error: global register variables are not supported
> register struct CPUX86State *env asm(AREG0);
>  ^
> (the full log is available in (1)). The closest I could find is stated
> in a posting from 2012 (2) where a similiar issue from seems to occur
> when Virtualbox is compiled with clang and not gcc. Not sure is this
> still applies today but Makefile seems still to refer --with-gcc.
>
> Some observations:
> * the build issue started when I included multimedia/kdenlive to the
> to-be-built port list
> * both ports (kdenlive and virtualbox-ose) share the Qt4 dependency
> * synth is building each port in a clean chroot, builds dependencies
> first and does a pkg install for them in the clean chroot where
> virtualbox-ose is built
> * kdenlive is built in order before virtualbox-ose, so Qt4 dependency
> build seems to be triggered from kdenlive
>
> Has anyone on this list an idea what is going wrong here?
>
> Thanks in advance & best regards,
> Matthias
>
>
> (1) https://dev.petermann-it.de/nextcloud/index.php/s/RpnDYYiyYSCjenb
> (2) http://osdir.com/ml/freebsd-emulation/2012-04/msg00108.html

The automated FreeBSD package building with poudriere produced the same error
last night for FreeBSD 10.3.

Since about a year the port uses a mixture of clang and gcc because clang does
not support global register variables. On the other side building all
ports with clang
but only vbox with gcc created issues in KDE.

The result are a couple of patches from jkim which are not supported
at all but use
both compilers in a mix. Might be they need to be fixed after the
update to vbox 5.0.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"