Re: net-im/pidgin-2.6.2
On Fri, October 2, 2009 9:33 am, Matthias Apitz wrote: > > Hello, > > The pidgin-2.6.2 sources (http://www.pidgin.im/) contain an important > fix for the problem that Yahoo! recently has changed something in the > protocol and old IM clients (like Kopete of KDE 3.5.10) can't connect > anymore to the Yahoo servers. > > I've fetched the sources directly (pidgin-2.6.2.tar.bz2) and they > configure and compile fine with the following options: > > $ ./configure --disable-vv --disable-nm --disable-tcl > $ gmake > # gmake install > > $ pidgin -v > Pidgin 2.6.2 (libpurple 2.6.2) > > The resulting IM client works fine with MSN and Yahoo. > > This morning I went to the FreeBSD ports collection server: > http://www.freebsd.org/cgi/ports.cgi?query=pidgin&stype=all > and there is a version 2.6.2 as well; I've fetched the tar ball of the > port in the hope that I will compile in my FreeBSD 8-CURRENT like the > above direct compile from source did. But the port-2.6.2 fetches older > sources (2.5.5) which does not contain the above mentioned fixes. > Why is this? That port includes the net-im/libpurple Makefile and that defines which version and distfile that is. So you would have to fetch that too and change the path where it is included ... very ugly. There are probably other dependencies updated too that you would also need to track manually. How about updating your ports tree as everybody else does? -- 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: p5-xmltv - old?
On Sun, November 15, 2009 12:24 am, Torfinn Ingolfsen wrote: > Hello, > > Is there a reason why p5-xmltv haven't been updated? In ports we have > version 0.5.52, but on the main web site version 0.5.56 have been > available a while now. > > Simply chnaging the version in the Makefile, removing the PORTREVISION > line and doing 'make makesum' get the port working: > r...@kg-quiet# diff -u p5-xmltv_0.5.52/Makefile p5-xmltv/Makefile > --- p5-xmltv_0.5.52/Makefile2009-10-18 10:26:10.0 +0200 > +++ p5-xmltv/Makefile2009-11-14 22:16:39.0 +0100 > @@ -6,8 +6,7 @@ > # > > PORTNAME=xmltv > -PORTVERSION=0.5.52 > -PORTREVISION=1 > +PORTVERSION=0.5.56 > CATEGORIES=textproc perl5 > MASTER_SITES=SF > PKGNAMEPREFIX=p5- > > Ok, It isn't perfect, it complains a bit when you install: > ===> Compressing manual pages for p5-xmltv-0.5.56 > gzip: can't stat: /usr/local/man/man1/tv_grab_be.1: No such file or > directory > gzip: can't stat: /usr/local/man/man1/tv_grab_br_net.1: No such file or > directory > gzip: can't stat: /usr/local/man/man1/tv_grab_dk.1: No such file or > directory > gzip: can't stat: /usr/local/man/man1/tv_grab_es.1: No such file or > directory > gzip: can't stat: /usr/local/man/man1/tv_grab_jp.1: No such file or > directory > ===> Registering installation for p5-xmltv-0.5.56 > > But it is a good starting point. Looks like MAN1 in the Makefile should be updated too. If it installs and deinstalls fine please submit it as PR. -- 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: p5-xmltv - old?
On Sun, November 15, 2009 6:27 pm, Torfinn Ingolfsen wrote:
> Hi,
>
> On Sun, Nov 15, 2009 at 12:16 PM, Bernhard Froehlich
> wrote:
>
>>
>> Looks like MAN1 in the Makefile should be updated too. If it installs
>> and
>> deinstalls fine please submit it as PR.
>>
>
> If anyone would test what I have so far (attached), it would help.
> It is tested with porttools ("port test" to be specific),and AFAICT passes
> ok.
> When properly tested, I will submit a PR.
>
> However, I am not really sure that we should upgrade without keeping the
> old
> port around.
> Why?
> Well, a few grabbers have disappeared from the new version, and I am not
> sure what ill effects that will have.
> For my country, tv_grab_no is replaced with tv_grab_no_gfeed. The new
> grabber is technically much better than the old one, but it have listings
> for fewer channels than the old one.
> For the other countries, I can only speculate. I see that tv_grab_be is
> missing from the new version, and don't know if there is a replacement.
>
> Any thoughts?
Builds fine in my 7-stable/i386 tinderbox. I've checked which ports are
depending on p5-xmltv [1] and checked if that update could affect them.
deskutils/ontv: NOTOK using tv_grab_be
misc/freeguide: OK using tv_cat
multimedia/freevo: OK using tv_cat
multimedia/mythtv: OK using tv_check
multimedia/tv_grab_au: OK using tv_check
The only one that definitely needs fixing is ontv. The others look good.
[1]
http://www.freshports.org/search.php?stype=depends_all&method=match&query=p5-xmltv&num=100&orderby=category&orderbyupdown=asc&search=Search
--
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"
Call for Testers: MythTV 0.22
MythTV 0.22 is ready for testing! They have done a lot of work to use Qt 4.4 and compiling mythtv has gotten a lot easier on FreeBSD with that. Nevertheless it is a huge application and needs compile and runtime testing on as many boxes as possible. I've already compiled on FreeBSD 8.0-RC1/amd64, FreeBSD 7.2/i386 and with a QATty tinderbox so i'm quite sure it will not look too bad. Runtime testing is about zero so we need feedback before we get it into the tree. Download: - http://home.bluelife.at/ports/mythtv-0.22-20091115.tar.gz Highlights: - enabled ivtv with patch from usleepless at gmail.com - Updated to 0.22 - http://www.mythtv.org/wiki/Release_Notes_-_0.22 - Qt 4.4 - DVB-S2 support (do we have a supported card on FreeBSD?) - hardware accelerated playback of H.264, MPEG-1/2, WMV, and VC-1 Testing it: # cd /tmp # fetch http://home.bluelife.at/ports/mythtv-0.22-20091115.tar.gz # cd /usr/ports/multimedia # tar xvf /tmp/mythtv-0.22-20091115.tar.gz # cd mythtv && make install Thanks! (Please reply to freebsd-multimedia@ only) -- 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: p5-xmltv - old?
On Mon, November 16, 2009 6:20 pm, Torfinn Ingolfsen wrote: > Hi, > > On Sun, Nov 15, 2009 at 8:10 PM, Bernhard Froehlich > wrote: > >> Builds fine in my 7-stable/i386 tinderbox. I've checked which ports are >> depending on p5-xmltv [1] and checked if that update could affect them. >> >> deskutils/ontv: NOTOK using tv_grab_be >> misc/freeguide: OK using tv_cat >> multimedia/freevo: OK using tv_cat >> multimedia/mythtv: OK using tv_check >> multimedia/tv_grab_au: OK using tv_check >> >> The only one that definitely needs fixing is ontv. The others look good. >> > > And that one (ontv) has gnome@ as the maintainer. > How should this be handled; should I send a mail to the gnome list first, > before sending in the PR? > Or should I just send the PR and then send a mail telling them that the > ontv port will / might be affected? Both should be valid but the former is probably a bit faster. At least tell someone of the gnome@ team about it. I've seen that the ontv version is already quite outdated so it probably makes sense to update it to the latest version when you're at it. So go ahead and contact the gnome@ people - irc is usually the fastest. -- 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 tester: VirtualBox 3.1.2 for FreeBSD
On Mon, December 28, 2009 3:25 pm, Gary Jennejohn wrote: > On Mon, 28 Dec 2009 00:24:26 +0100 > Martin Wilke wrote: > >> # /usr/local/etc/rc.d/vboxguest.sh start >> > > This shell script has a problem. It looks in /boot/kernel for the > module but the port installs it under /boot/modules. > > I also can't load this module (after loading vboxdrv.ko): > > sh -x /usr/local/etc/rc.d/vboxguest.sh start > + VBOXGUESTFILE='' > + SILENTUNLOAD='' > + check_root > + id -u > + test 0 -ne 0 > + get_module_path > + moduledir=/boot/modules > + modulepath=/boot/modules/vboxguest.ko > + test -f /boot/modules/vboxguest.ko > + VBOXGUESTFILE=/boot/modules/vboxguest.ko > + check_if_installed > + test /boot/modules/vboxguest.ko -a -f /boot/modules/vboxguest.ko > + return 0 > + test '' = silentunload > + start > + module_loaded > + kldstat > + grep vboxguest > + loadentry='' > + test -z '' > + return 1 > + /sbin/kldload vboxguest.ko > kldload: can't load vboxguest.ko: Exec format error > + module_loaded > + kldstat > + grep vboxguest > + loadentry='' > + test -z '' > + return 1 > + abort 'Failed to load vboxguest.' > + echo 'Failed to load vboxguest.' > Failed to load vboxguest. > + exit 1 > > file /boot/modules/vbox*.ko > /boot/modules/vboxdrv.ko:ELF 64-bit LSB relocatable, x86-64, version 1 > (FreeBSD), not stripped > /boot/modules/vboxguest.ko: ELF 64-bit LSB relocatable, x86-64, version 1 > (FreeBSD), not stripped > /boot/modules/vboxnetadp.ko: ELF 64-bit LSB relocatable, x86-64, version 1 > (FreeBSD), not stripped > /boot/modules/vboxnetflt.ko: ELF 64-bit LSB relocatable, x86-64, version 1 > (FreeBSD), not stripped > > Does vboxguest.ko have silent dependencies on other vbox modules? I only > loaded vboxdrv.ko. Looks like you installed the guest additions on the host. You should not do that. They should only be installed on FreeBSD guests running in an virtualbox. Nevertheless could you please see in /var/log/messages what error was logged when you tried to load vboxguest.ko ? -- 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 tester: VirtualBox 3.1.2 for FreeBSD
On Mon, December 28, 2009 7:24 pm, Doug Barton wrote: > Bernhard Froehlich wrote: >> Looks like you installed the guest additions on the host. You should not >> do that. They should only be installed on FreeBSD guests running in an >> virtualbox. > > The pkg-descr and COMMENT should probably be amended to reflect this > since it was confusing to me too. :) Perhaps something like the attached? > > Also, in looking at the shell script that is provided for the > additions it would be nice if it could be updated to an rc.d style > script. If anyone wants to tackle that and needs help feel free to > follow up on the -ports list, or freebsd...@freebsd.org. Thanks. I've applied the patch and will write a new rc.d startscript for the guest additions. Looks like they need a bit love anyway. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=607 -- 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 tester: VirtualBox 3.1.2 for FreeBSD
On Tue, January 5, 2010 9:18 am, Eirik Øverby wrote:
> Hi,
>
> On 28. des. 2009, at 00.24, Martin Wilke wrote:
>
>> - Install new port:
>># cd ../virtualbox-ose-kmod && make install clean
>># cd ../virtualbox-ose && make install clean
>
> At this point, the install fails like thus:
>
> running install_egg_info
> Removing /usr/local/lib/python2.6/site-packages/vboxapi-1.0-py2.6.egg-info
> Writing /usr/local/lib/python2.6/site-packages/vboxapi-1.0-py2.6.egg-info
> (cd
> /root/vbox/virtualbox-ose/work/VirtualBox-3.1.2_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/python
> && /bin/sh -c '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1
> >/dev/null 2>&1) && /usr/sbin/chown -R root:wheel $1 && /usr/bin/find
> -d $0 $2 -type d -exec chmod 755 $1/{} \; && /usr/bin/find -d $0 $2 -type
> f -exec chmod 444 $1/{} \;' -- "*" /usr/local/lib/python2.6/site-packages)
> /usr/local/bin/python2.6 -mcompileall
> /usr/local/lib/python2.6/site-packages/xpcom/
> Listing /usr/local/lib/python2.6/site-packages/xpcom/ ...
> Listing /usr/local/lib/python2.6/site-packages/xpcom/client ...
> Listing /usr/local/lib/python2.6/site-packages/xpcom/server ...
> pw: group 'vboxusers' already exists
> Adding group "vboxusers" failed...
> *** Error code 1
>
> Stop in /root/vbox/virtualbox-ose.
> *** Error code 1
>
> Stop in /root/vbox/virtualbox-ose.
>
> The vboxusers group does indeed exist:
> vboxusers:*:920:
> but has no users. Adding myself changes nothing.
Looks a bit weird. The install script only needs and creates a vboxusers
group so that it can install the files with the correct ownership. But it
checks first if the group exists and that check seems to fail for an
unknown reason. Could you please send back the output of the following 3
commands? (as root)
pw group show vboxusers; echo $?
pw groupadd vboxusers -g 920
grep vbox /etc/group
> Should I install the current version from ports first, before trying to
> ugprade to this snapshot?
I think that should not change anything because the install script did not
change for a long time.
My guess at the moment is that something in your /etc/group is
inconsistent or wrong so that the tools get confused.
--
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: Redmine files not executable, but log files are executable
On Fri, 05 Feb 2010 01:07:43 +0100, Miroslav Lachman <000.f...@quip.cz>
wrote:
> Hi,
>
> I am new to installation of www/redmine from ports. I am surprised that
> all redmine files are not executable. Including files which should be
> executed by startup script etc. (I mean files in script/ directory,
> mainly script/server)
> These files are executables in the original source tar archive.
>
> What is more surprising is that after reinstall or upgrade of redmine,
> there are executable bits set on logfiles, because of recursive chmod in
> redmine/Makefile:
>
> .for f in files log tmp public/plugin_assets
> ${CHMOD} -R 755 ${WWWDIR}/${f}
> .endfor
>
> redmine/# find . -type f -perm +0111 -ls
> 321080 2 -rwxr-xr-x 1 www www 374 May 28 2009
> ./public/plugin_assets/README
> 14111 2 -rwxr-xr-x 1 www www 36 Sep 13 14:10 ./files/delete.me
> 321079 2 -rwxr-xr-x 1 www www 51 May 28 2009
./log/production.log
> 14119 2 -rwxr-xr-x 1 www www 36 Sep 13 14:10 ./log/delete.me
>
>
> I know that the first problem is caused by COPYTREE_SHARE in do-install:
> and I am asking if it is really necesarry to have all files set to 0444,
> I think those few files should be installed executable as in the
> original archive.
> And chmod for directories should be not recursive to not set executable
> bits on files from previous installation.
>
> So my proposal is use chmod without -R on directories only:
>
> .for f in files log tmp tmp/cache tmp/sessions tmp/sockets
> public/plugin_assets
> ${CHMOD} 755 ${WWWDIR}/${f}
> .endfor
>
> And to set 0554 on files in scripts/ directory
>
> .for f in about breakpointer console destroy generate plugin runner
server
> ${CHMOD} 0555 ${WWWDIR}/script/${f}
> .endfor
>
> (and maybe some files in script/performance + script/process too)
>
> What you think about that?
Yes, that's true. All files should be non executable beyond /usr/local/www
so the COPYTREE_SHARE is right but the chmod -R should only be made for
directories and is obviously wrong.
Scripts shouldn't be beyond /usr/local/www. Honestly I've never used one
of
them so I'm not sure if they do work at all. It's probably better to have
them somewhere else but they do use relative paths to include code so they
are obviously not designed to work anywhere else outside of the redmine
paths.
The log directory should be in /var/log/redmine too so it looks like it's
time
to split the redmine directories up and have some deeper thought about the
port.
I don't know what webserver redmine admins expect and how they integrate
it
into their configuration. Personally I've written a startscript that uses
www/rubygem-thin as webserver behind nginx but the out of the box version
is
mongrel. Haven't decided yet what to do but i could write startscripts for
common ruby servers and let the user choose with option he wants.
Thanks for the report and i will have a look at the issues soon.
--
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: FreeBSD Port: virtualbox-ose-3.1.4
On Tue, 16 Mar 2010 09:51:59 -0400, William DiNoia wrote: > I'm getting an Error code 71 while building virtualbox-ose: > > /bin/ln -sf /usr/local/lib/virtualbox/VBoxSDL /usr/local/bin/ > install -s -o root -g wheel -m 555 > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.4_OSE/out/freebsd.x86/release/bin/VBoxTestOGL > > /usr/local/lib/virtualbox/ > install: > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.4_OSE/out/freebsd.x86/release/bin/VBoxTestOGL: > > No such file or directory > *** Error code 71 > > Stop in /usr/ports/emulators/virtualbox-ose. > *** Error code 1 > > Stop in /usr/ports/emulators/virtualbox-ose. > > ===>>> Installation of virtualbox-ose-3.1.4 (emulators/virtualbox-ose) > failed > ===>>> Aborting update > > ===>>> complete Could you send us the output of "make showconfig" from the virtualbox-ose port and the build log? It looks like a problem with OpenGL detection. -- 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 port fail freebsd 8.1-prerelease
On Tue, 25 May 2010 15:03:49 -0400, Jorge Medina wrote: > r...@rusty% uname -a > FreeBSD rusty.engine.cl 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Sat > May 22 20:30:36 CLT 2010 > r...@rusty.engine.cl:/usr/obj/usr/src/sys/GENERIC amd64 > > r...@rusty% cd /usr/ports/emulators/virtualbox > r...@rusty% make install clean > ===> virtualbox-3.0.51.r22902_2 depends on executable: yasm - found > ===> virtualbox-3.0.51.r22902_2 depends on executable: as86 - found > ===> virtualbox-3.0.51.r22902_2 depends on executable: xsltproc - found > ===> virtualbox-3.0.51.r22902_2 depends on executable: kmk - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/easy_install-2.6 - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/python2.6 - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/libdata/pkgconfig/xcursor.pc - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/libdata/pkgconfig/xmu.pc - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/lib/qt4/libQtGui.so - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/linguist-qt4 - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/moc-qt4 - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/lib/qt4/libQtNetwork.so - found > ===> virtualbox-3.0.51.r22902_2 depends on file: /usr/local/bin/rcc - > found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/uic-qt4 - found > ===> virtualbox-3.0.51.r22902_2 depends on file: > /usr/local/bin/sdl-config - found > ===> virtualbox-3.0.51.r22902_2 depends on executable: pkg-config - found > ===> virtualbox-3.0.51.r22902_2 depends on executable: cdrecord - found > ===> virtualbox-3.0.51.r22902_2 depends on shared library: png.5 - not > found > ===>Verifying install for png.5 in /usr/ports/graphics/png > ===> Returning to build of virtualbox-3.0.51.r22902_2 > Error: shared library "png.5" does not exist > *** Error code 1 Wow, you are using an really old version of vbox. It is a quickly moving target and I would not recommend to use anything older than the latest port if absolutely neccessary. It looks like you have updated everything including png but vbox so this is not supported at all. Please update your ports tree to a consistent state. -- 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: Solutions for the PR load problem
On Sat, 10 Jul 2010 11:00:38 +0200, Lars Engels wrote: > On Fri, Jul 09, 2010 at 10:51:01PM +0200, Dominic Fandrey wrote: >> On 09/07/2010 22:00, Shaun Amott wrote: >> > >> > I'm not sure how many non-committers were aware of / given access to >> > tb3 >> > and tb4 when they were around, but if tinderbox were used as a matter >> > of >> > course, it would, I believe go some way to speeding things up. >> > >> >> So if I set up a private tinderbox and provide amd64 and i386 >> 6-/7-/8-stable logs with every PR I submit it would hasten the >> processing of my PRs? > > The more complex a port is and the more dependencies it has the more > work a committer has to check if the PR is error-free. > Having TB-Logs would prove that the port builds fine, and the PR is more > likely to be taken. Exactly for this reason beat@ has created a Tinderbox Virtual Machine for virtualbox. So port maintainers can test their updates in a tinderbox and discover problems earlier without the need of a dedicated tinderbox machine and all the setup woes. http://vboxtindi.chruetertee.ch/ -- 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: XBMC port
On Tue, 5 Oct 2010 12:37:19 +0200, Mickaël Maillot wrote: > hi, > > you can test my pre version of xbmc port > > some infos: > - i host xbmc files because i can't find a recent tar.gz > - internal video player crash on my intel graphic, you can use mplayer > as external video player > ex: http://fneufn.eu/freebsd/xbmc/playercorefactory.xml in ~/.xbmc/userdata/ > - vdpau works fine > - skin aeon65 crash xbmc > - only python 2.4, 2.5 and 2.6 are supported > - with pulse, i can choose /dev/dsp audio output > - good luck with custom alsa output (ex: alsa:surround51 works) > - if you want correct utf8, start xbmc with: > LANG=fr_FR.UTF-8 /usr/local/bin/xbmc/xbmc.sh > - xbmc.bin need XBMC_BIN_HOME and XBMC_HOME defined to start > defaults are (already added in xbmc.sh): > XBMC_BIN_HOME=/usr/local/lib/xbmc > XBMC_HOME=/usr/local/share/xbmc > - timezone doesn't work > - plist without: faac, hal, nonfree or avahi option can be wrong > > > The port can be downloaded from: > http://fneufn.eu/freebsd/xbmc/xbmc.shar Thank you very much for your work! Port and patches look already quite good so I will give it some testing over the next few days in Karlsruhe. Have you already compiled it on amd64 and i386? -- 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: XBMC port
On Tue, 5 Oct 2010 12:37:19 +0200, Mickaël Maillot wrote: > hi, > > you can test my pre version of xbmc port > > some infos: > - i host xbmc files because i can't find a recent tar.gz > - internal video player crash on my intel graphic, you can use mplayer > as external video player > ex: http://fneufn.eu/freebsd/xbmc/playercorefactory.xml in ~/.xbmc/userdata/ > - vdpau works fine > - skin aeon65 crash xbmc > - only python 2.4, 2.5 and 2.6 are supported > - with pulse, i can choose /dev/dsp audio output > - good luck with custom alsa output (ex: alsa:surround51 works) > - if you want correct utf8, start xbmc with: > LANG=fr_FR.UTF-8 /usr/local/bin/xbmc/xbmc.sh > - xbmc.bin need XBMC_BIN_HOME and XBMC_HOME defined to start > defaults are (already added in xbmc.sh): > XBMC_BIN_HOME=/usr/local/lib/xbmc > XBMC_HOME=/usr/local/share/xbmc > - timezone doesn't work > - plist without: faac, hal, nonfree or avahi option can be wrong > > > The port can be downloaded from: > http://fneufn.eu/freebsd/xbmc/xbmc.shar Thanks for your work. I had a look at the port and there are a few things that we should resolve before the port is ready to get it into the tree. - add missing libltdl dependency (patch attached) - add missing runtime dependency glxinfo (graphics/mesa-demos) - fix graphics/mesa-demos port which is currently marked broken - fix the compile problem in xbmc/cores/paplayer/SIDCodec (had a look but could not find it yet) - what does the NONFREE option mean? should we restrict the port? any problems redistributing the distfile? - find a better solution for the int casts because of the different size of DWORD on linux and BSD - port should use the upcoming release branch [1] or better the beta release tags from [2] (not sure which one you use currently, trunk?) [1] http://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/Dharma/ [2] http://xbmc.svn.sourceforge.net/svnroot/xbmc/tags/Dharma_beta3/ -- Bernhard Froehlich http://www.bluelife.at/ xbmc-fixes.diff Description: Binary data ___ 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 UI and remote X clients
On Fri, 22 Oct 2010 15:02:20 -0500, Ade Lovett wrote: > Folks, > > It would appear that ever since 3.2.8_1 of virtualbox-ose, a number > of additions were made to unconditionally enable some kind of hardware > acceleration in the UI. > > This completely breaks the UI with a variety of QT errors, when > running on a remote X11 displays, so far I've tested X11.app and > XQuartz.app on OSX, cygwin/X on Windows 7/XP, and even an Xvnc server > running on a FreeBSD/amd64 box. Could you please post that errors? It sounds like an upstream bug so it would be good to collect a few details like why it happens on your system bug I cannot reproduce it here with Intel graphics. Do you probably have nvidia graphics or anything special? Maybe the bug you are hitting was already fixed upstream so could you test the virtualbox-ose-devel port [1] and see if the problem persists? Sure we could make an option for that patch or revert it but that won't fix the underlying problem that it uncovered. So I would really like to get it at least analyzed first and if it cannot get fixed we can always disable it. [1] http://svn.bluelife.at/nightlies/virtualbox-port.tar.gz -- 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 UI and remote X clients
On Fri, 22 Oct 2010 17:04:35 -0500, Ade Lovett wrote: > On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote: >> Could you please post that errors? > > freebsd% setenv DISPLAY remote:0 > freebsd% VirtualBox > > Wait for UI to pop up, click on 'Settings' for any virtual host, > VirtualBox crashes with: > > Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid context current. > Segmentation fault > > > (remote) in this case has been (so far): > > MacOSX 10.6 with Apple's X11.app > MacOSX 10.6 with XQuartz.app > Windows XP with cygwin/X > Windows 7 with cygwin/X > Xvnc on the FreeBSD box, then using either the Mac or Windows box to > fire up a vnc client to get to the Xvnc. That makes more sense now. Looks like the 2D acceleration unconditionally requires OpenGL. You will find a lot of MythTV users with exactly that problem and they usually switch to Qt rendering. Don't know if vbox has such a possibility. I think it makes sense to add an OpenGL option that disables it all together. Can you try if it works for you when you reenable VIDEOHWACCEL in the Makefile and add CONFIGURE_ARGS+=--disable-opengl somewhere? >> It sounds like an upstream bug so it >> would be good to collect a few details like why it happens on your >> system bug I cannot reproduce it here with Intel graphics. > > Please re-read what I said. The host machine (running the > virtualboxes) has NO graphics of any kind. It's FreeBSD > 8.1-STABLE/amd64 hooked up to a VT320 terminal as a serial console. > It has X11 libraries and the various toolkits (QT etc) installed, but > no Xorg server (other than Xvnc), no X11 drivers > (graphics/keyboard/mouse). > > 3.2.8 was fine > 3.2.8_1 broke things > 3.2.10 (unsurprisingly) hasn't changed -- 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 UI and remote X clients
On Sat, 23 Oct 2010 17:29:15 -0500, Ade Lovett wrote: > On Oct 23, 2010, at 03:28 , Bernhard Froehlich wrote: >> I think it makes sense to add an OpenGL option that disables it all >> together. Can you try if it works for you when you reenable VIDEOHWACCEL >> in the Makefile and add CONFIGURE_ARGS+=--disable-opengl somewhere? > > I forcibly added --disable-opengl and recompiled. Same error. Looks > like it's going to be a bit more tricky than that. I think i've found the reason why it did not work. Please add --disable-opengl and also add the attached patch. http://home.bluelife.at/patches/vbox-2dacc-opengl.diff -- Bernhard Fröhlich http://www.bluelife.at/ vbox-2dacc-opengl.diff Description: Binary data ___ 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: vbox-manager shows nissan.de as background
On Wed, 24 Aug 2011 23:38:59 +0200, Norbert Augenstein wrote: > Hi list, > > i was suprised to see the nissan.de webpage starting up > in the background of my Virtualbox-Manager window. > I coud not create a screenshot, i had to use my camera:) > > www.augenstein.net/auge/vbox_nissan.jpg > > > rebuilding vbox and/or the kernel module does not help. > Does anyone else see this? This looks a lot like an known nvidia rendering corruption problem that I have also seen on Linux. There is some common setting for xorg.conf to disable some option but I cannot recall which one exactly right now. I've also learned quite recently that a similar problem exists for Intel IGP and they also have an xorg.conf option for 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: FreeBSD Port: xbmc-10.1_2
On Thu, 8 Sep 2011 13:02:56 +0200, emil vanherp wrote: > Hi > > XBMC seems to depend on sqlite3 (it won't compile without) but it's not on > the dependencies list. Don't know why you think it's missing but that's plain wrong. It's there at the bottom of the LIB_DEPENDS. http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/xbmc/Makefile?rev=1.11 -- 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: FreeBSD Port: redmine-1.2.1_1
On Sat, 10 Sep 2011 12:10:08 +0200, Wim De Nocker wrote: > have tried to install the current port version on several systems now. > All attempt failed. > No fresh install is possible (Freebsd 8.1, 8.2, 7.1), and using > portupgrade/portmaster also breaks Redmine. > > Ruby version is at > # ruby 1.8.7 (2011-06-30 patchlevel 352) [i386-freebsd8] > > all the way I get errors saying > Gem::SourceIndex#add_spec called from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:91. > NOTE: Gem::SourceIndex#add_spec is deprecated, use > Specification.add_spec. It will be removed on or after 2011-11-01. > > and additional > => Rails 2.3.11 application starting on http://0.0.0.0:3000 > /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:277:in > `==': undefined method `name' for "actionmailer":String > (NoMethodError) > from > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in `===' Haven't got those messages yet but something like this: undefined method `name' for "daemons":String /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:277:in `==' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in `===' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in `matching_specs' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `find_all' /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:410:in `each' /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:409:in `each' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:216:in `find_all' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:216:in `matching_specs' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:238:in `to_specs' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:256:in `to_spec' /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:1200:in `gem' /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:75:in `add_load_paths' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in `add_gem_load_paths' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in `each' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in `add_gem_load_paths' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:132:in `process' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:113:in `send' /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:113:in `run' /usr/local/www/redmine/config/environment.rb:20 Well obviously someone broke redmine _again_! So I've CC'd ruby@ because they should at least know when they break something though they usually don't care about 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: FreeBSD Port: redmine-1.2.1_1
On Sat, 10 Sep 2011 15:47:48 +0200, Bernhard Froehlich wrote: > On Sat, 10 Sep 2011 12:10:08 +0200, Wim De Nocker wrote: >> have tried to install the current port version on several systems now. >> All attempt failed. >> No fresh install is possible (Freebsd 8.1, 8.2, 7.1), and using >> portupgrade/portmaster also breaks Redmine. >> >> Ruby version is at >> # ruby 1.8.7 (2011-06-30 patchlevel 352) [i386-freebsd8] >> >> all the way I get errors saying >> Gem::SourceIndex#add_spec called from >> /usr/local/lib/ruby/site_ruby/1.8/rubygems/source_index.rb:91. >> NOTE: Gem::SourceIndex#add_spec is deprecated, use >> Specification.add_spec. It will be removed on or after 2011-11-01. >> >> and additional >> => Rails 2.3.11 application starting on http://0.0.0.0:3000 >> /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:277:in >> `==': undefined method `name' for "actionmailer":String >> (NoMethodError) >> from >> /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in `===' > > Haven't got those messages yet but something like this: > > undefined method `name' for "daemons":String > /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:277:in > `==' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in `===' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:217:in > `matching_specs' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in > `find_all' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:410:in > `each' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:409:in > `each' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:216:in > `find_all' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:216:in > `matching_specs' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:238:in > `to_specs' > /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:256:in > `to_spec' > /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:1200:in `gem' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:75:in > `add_load_paths' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in > `add_gem_load_paths' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in > `each' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:301:in > `add_gem_load_paths' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:132:in > `process' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:113:in > `send' > /usr/local/www/redmine/config/../vendor/rails/railties/lib/initializer.rb:113:in > `run' > /usr/local/www/redmine/config/environment.rb:20 > > > Well obviously someone broke redmine _again_! So I've CC'd ruby@ > because they should at least know when they break something though they > usually don't care about it. It turned out that this problem is a regression in RubyGems 1.8 and hasn't been fixed upstream yet. http://rubyforge.org/tracker/index.php?func=detail&aid=29188&group_id=126&atid=575 The temporary workaround is to downgrade devel/ruby-gems to 1.7.2 so I've created an port for that out of the history: http://home.bluelife.at/patches/ruby-gems-1.7.2-port.tar.gz There is no need to reinstall any of the installed gems. I will mark the port as BROKEN for now until a fix for RubyGems 1.8.x is available or someone finds a workaround for 1.8. -- 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-kmod fails to build on -CURRENT
On 31.10.2011 10:23, Marco Steinbach wrote:
Vladimir Kushnir wrote on 26.10.2011 11:32:
Hi
Well, the problem is:
I'm trying to build VirtualBox{*} on amd64 10.0-CURRENT. The very
first port, virtualbox-ose-kmod fails with
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE/out/freebsd.
amd64/release/bin/src/vboxdrv/freebsd/SUPDrv-freebsd.c:104: error:
'D_PSEUDO' undeclared here (not in a function)
And indeed, threre's no D_PSEUDO flags in /usr/src
Any help?
Thanks in advance,
Vladimir
See http://svnweb.freebsd.org/base?view=revision&revision=226500
I presume emulators/virtualbox-ose-kmod needs to take this one into
account.
I've submitted a PR.
My first guess is that it could be enough to remove the flag but I
don't know if we need to replace some code with make_dev_p(). So i've
CC'd ed@ and hope that he can shed some light on that.
https://www.virtualbox.org/browser/trunk/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c#L104
--
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 fails on HEAD
On 13.11.2011 02:26, Doug Barton wrote: On 11/12/2011 00:03, Bernhard Fröhlich wrote: look for the patch in ports/162186 Thanks. I found the patch, but if I download it and turn it into patch-foo and try to build the port, all hunks fail to apply. Normally I'd just apply by hand and regenerate, but it's a big patch. Has anyone produced a working version? That's because of the windows line endings. Don't know where they came from but this patch applies fine now for 4.0.12 and 4.1.4. http://home.bluelife.at/patches/patch-cdev-fixes.diff -- 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: [removed ports] sysutils/cpuburn
On 15.11.2011 16:07, Baptiste Daroussin wrote: On Tue, Nov 15, 2011 at 04:34:22PM +0200, Andriy Gapon wrote: Does anyone know good any alternative(s) for cpuburn? If not, then I would like to request that this port be restored. I am prepared to be designated as its maintainer and to host its distfile (via my FreeBSD account). Maintaining the port should be rather easy as it can not have any security issues by definition and at the moment there is no active upstream, so no code changes are expected. P.S. Sorry that I've missed its deprecation. I haven't noticed the activity until I needed to use it at yet another system. I often use sysutils/stress don't know if that fits your needs? I've just noticed that cpuburn is gone and stress is not an alternative for my task. Why? Because I use cpuburn to verify the undervolting capabilities of AMD cpus's for sysutils/cpupowerd which needs to explicitly hammer the CPU with MMX instructions and parallel with normal CPU instructions while lowering vcore. -- 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: xbmc pvr in ports; update, please test with MythTV too! :)
On 05.12.2011 19:56, Juergen Lock wrote: On Sat, Nov 19, 2011 at 12:37:19PM +0100, Juergen Lock wrote: Hi! So I learned there are actually releases of xbmc pvr already, which means nothing should stop us from committing it to ports too? :) Now I'm wondering if this needs to be repocopied from the xbmc port first since it's kind of a fork... Few patches still apply and I see libreoffice also wasn't repocopied from openoffice, so maybe not? The patch against the xbmc port is here: http://people.freebsd.org/~nox/tmp/xbmc-pvr-ppa-odk55.patch (I just see I haven't added CONFLICTS_INSTALL with xbmc yet, will do that later.) It still seems to work with my older xvdr addon and vdr plugin ports, but maybe I should update those again too before committing: http://people.freebsd.org/~nox/tmp/xbmc-addon-xvdr.shar http://people.freebsd.org/~nox/tmp/vdr-plugin-xvdr.shar Of course everyone is welcome to test... :) (I only tested with vdr, not with mythtv.) Juergen I just updated to the latest release pvr-ppa-odk56: http://people.freebsd.org/~nox/tmp/xbmc-pvr-ppa-odk56.patch It would be nice if someone could verify this works with mythtv too before I commit it... Wow this is a pretty big update. Are you sure this is the way to go with the original multimedia/xbmc port? I would prefer sticking to the upstream version with multimedia/xbmc and have such an custom branch in another port that also reflects this from the name. Do you know about the xbmc-devel port that he maintains on redports? http://redports.org/browser/fneufneu/multimedia -- 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: xbmc pvr in ports; update, please test with MythTV too! :)
On 05.12.2011 19:56, Juergen Lock wrote: I just updated to the latest release pvr-ppa-odk56: http://people.freebsd.org/~nox/tmp/xbmc-pvr-ppa-odk56.patch It would be nice if someone could verify this works with mythtv too before I commit it... First thing I noticed was that XBMC_Mythtv.pvr should really be XBMC_MythTV.pvr because it complains in the logfile when loading the addon: ERROR: ADDON: Could not locate XBMC_MythTV.pvr Moving the file to /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr gets it a step further. Next thing is an undefined symbol: ERROR: Unable to load /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr, reason: /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr: Undefined symbol "_ZTI14MythXmlCommand" It looks like this is part of libmythxml but It was not linked to the shared object. While searching for that problem I found the following commit which includes a hunk for xbmc/pvrclients/mythtv/Makefile.in and looks pretty right in what it does. But it's quite different code than what you have in your port. Are you sure you aren't using an old branch for the PVR code? http://xbmc.git.sourceforge.net/git/gitweb.cgi?p=xbmc/xbmc;a=patch;h=7e83f17 Both problems fixed with the attached patch. Now getting to the next undefined symbol: ERROR: Unable to load /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr, reason: /usr/local/lib/xbmc/add ons/pvr.mythtv/XBMC_MythTV.pvr: Undefined symbol "GetChannelsAmount" -- Bernhard Fröhlich http://www.bluelife.at/ patch-xbmc-pvrclients-mythtv-Makefile.in Description: Binary data ___ 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: xbmc pvr in ports; update, please test with MythTV too! :)
On 12.12.2011 13:26, Bernhard Froehlich wrote: On 05.12.2011 19:56, Juergen Lock wrote: I just updated to the latest release pvr-ppa-odk56: http://people.freebsd.org/~nox/tmp/xbmc-pvr-ppa-odk56.patch It would be nice if someone could verify this works with mythtv too before I commit it... First thing I noticed was that XBMC_Mythtv.pvr should really be XBMC_MythTV.pvr because it complains in the logfile when loading the addon: ERROR: ADDON: Could not locate XBMC_MythTV.pvr Moving the file to /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr gets it a step further. Next thing is an undefined symbol: ERROR: Unable to load /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr, reason: /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr: Undefined symbol "_ZTI14MythXmlCommand" It looks like this is part of libmythxml but It was not linked to the shared object. While searching for that problem I found the following commit which includes a hunk for xbmc/pvrclients/mythtv/Makefile.in and looks pretty right in what it does. But it's quite different code than what you have in your port. Are you sure you aren't using an old branch for the PVR code? http://xbmc.git.sourceforge.net/git/gitweb.cgi?p=xbmc/xbmc;a=patch;h=7e83f17 Both problems fixed with the attached patch. Now getting to the next undefined symbol: ERROR: Unable to load /usr/local/lib/xbmc/addons/pvr.mythtv/XBMC_MythTV.pvr, reason: /usr/local/lib/xbmc/add ons/pvr.mythtv/XBMC_MythTV.pvr: Undefined symbol "GetChannelsAmount" I got the plugin load correctly now with another patch that is attached. After setting the PIN in mythtv-setup it also connects fine to the backend now but I cannot import any channels into xbmc so I cannot even test watching TV. It feels a lot like the code is unfinished or unmaintained and not expected to work with mythtv 0.24. The future also doesn't look good because I found in the MythTV wiki (http://www.mythtv.org/wiki/Category:MythXML): The MythXML interface has been rewritten for upcoming 0.25, and these methods will no longer be valid. So the xbmc pvr plugin for mythtv is kind of useless. -- Bernhard Fröhlich http://www.bluelife.at/ patch-xbmc-pvrclients-mythtv-client.cpp Description: Binary data ___ 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"
redports.org - The public FreeBSD ports development infrastructure
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! In case you never heard of it before redports is the result of an idea born at EuroBSDCon 2011 in Karlsruhe to give Port Maintainers and Port Committers a public service to test their new ports or ports patches during development or before submitting a ports PR. Many people test ports only on their own machine because of lack of hardware. Redports gives you instant access to build environments for FreeBSD 7.4, 8.2, 9-CURRENT, 10-CURRENT on i386 and amd64 and even special ones that use CLANG/LLVM or GCC 4.5 as ports compiler. For everyone familiar with FreeBSD Ports Tinderbox [1] it's pretty obvious how it works. In fact redports is build on top of multiple Tinderboxes so it is scalable, fast and reliable. With your account you get your own Subversion Repository to maintain your ports and with every commit to the repository all affected ports are automatically built. When registering an account please read the UserGuide [2] first to get an idea of how to work with it. Feedback and new Ideas are welcome! Best regards, Bernhard Fröhlich (decke@) [1] http://tinderbox.marcuscom.com/ [2] http://redports.org/wiki/UserGuide -- 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 - The public FreeBSD ports development infrastructure
On 01.01.2012 21:03, Vitaly Magerya wrote: Hi again. I've got this issue: an update to one port depends on an update to another one, and I'd like to test both before submitting. So the question is this: if I've got both ports in the repository, when rebuilding the dependent port, will redports use the dependency from official ports tree, or from my repository? Redports will use your whole repository as an overlay to the original ports tree but it also caches already build packages based on PKGVERSION. So if you have a port in your tree which is different from the original port then you should take care that you bump PORTREVISION or PORTVERSION/DISTVERSION. To do what you want just commit both ports to your tree and trigger a build of the slave port. You can verify that everything was as expected by looking at the buildlog where you can see which packages in which versions were used as dependency. -- 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, vboxwebsrv and VRDPAuth
On 02.01.2012 22:23, Marek Salwerowicz wrote: Hi all, My host is 9.0-RC3 amd64. I've installed VirtualBox from /usr/ports/emulation/virtualbox-ose port, with GUESTADDITIONS, DBUS, VNC and WEBSERVICE options. I have problem with authenticating user for using the VirtualBox web service. When I set: freebsde64# VBoxManage setproperty websrvauthlibrary null everything works - I am able to connect to webservice and manage machines (I tested phpvirtualbox also) But after setting: freebsde64# VBoxManage setproperty websrvauthlibrary default and running vboxwebsrv, I am not able to connect to web service (despite giving right credentials). The output from vboxwebsrv -v is as follows: 00:00:09.312 SQW01external authentication library is 'VBoxAuth' 00:00:09.312 SQW01authenticate(): Could not resolve import 'VRDPAuth2'. Error code: VERR_SYMBOL_NOT_FOUND 00:00:09.312 SQW01authenticate(): Could not resolve import 'VRDPAuth'. Error code: VERR_SYMBOL_NOT_FOUND 00:00:09.312 SQW01authenticate(): result of AuthEntry(): 0 00:00:09.312 SQW01-- leaving __vbox__IWebsessionManager_USCORElogon, rc: 0x80004005 As I got know, VRDPAuth is PAM library for authenticating users - but I can't find it in my host system - how can I install it? My second problem is (connected with the first one as I suppose) that even despite setting '--vrde on' option (and port also) I am not able to connect to guest machine from my other computer (Windows 7 RDP Client) Looking forward to hearing from you any suggestions. VRDP is closed source and included in the Oracle VM VirtualBox Extension Pack which is not available for FreeBSD. -- 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.org - The public FreeBSD ports development infrastructure
On 02.01.2012 23:32, Doug Barton wrote: Is there such a thing as a redports mailing list? No, currently not. There is no mail infrastructure for redports yet. If people want such a list or an IRC channel I could certainly do it but it's not high priority for me right 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.org - The public FreeBSD ports development infrastructure
On 03.01.2012 22:32, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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! In case you never heard of it before redports is the result of an idea born at EuroBSDCon 2011 in Karlsruhe to give Port Maintainers and Port Committers a public service to test their new ports or ports patches during development or before submitting a ports PR. [...] Wow! Stellar job, Bernhard, and I'm looking forward to using redports.org for fixing ports that are broken under clang. Hope you don't want to do that today because during the night the current building machine paniced and needs someone power cycling it. I will do this in the evening so no builds today :( It looks like I could get some hardware from portmgr so hopefully more hardware and redundancy is available soon. I noticed one minor typo on https://redports.org/buildgroups: automaticaly -> automatically Thanks, it's fixed 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.org - The public FreeBSD ports development infrastructure
On 02.01.2012 23:32, Doug Barton wrote: Is there such a thing as a redports mailing list? I neither have the infrastructure nor the time to setup and maintain my own list so I created one on Google Groups: redpo...@googlegroups.com https://groups.google.com/group/redports IRC was easy: #redports on Freenode irc://irc.freenode.net#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: redports.org - The public FreeBSD ports development infrastructure
On 04.01.2012 19:21, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/4/12 3:07 AM, Bernhard Froehlich wrote: On 03.01.2012 22:32, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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! In case you never heard of it before redports is the result of an idea born at EuroBSDCon 2011 in Karlsruhe to give Port Maintainers and Port Committers a public service to test their new ports or ports patches during development or before submitting a ports PR. [...] Wow! Stellar job, Bernhard, and I'm looking forward to using redports.org for fixing ports that are broken under clang. Hope you don't want to do that today because during the night the current building machine paniced and needs someone power cycling it. I will do this in the evening so no builds today :( It looks like I could get some hardware from portmgr so hopefully more hardware and redundancy is available soon. I noticed one minor typo on https://redports.org/buildgroups: automaticaly -> automatically Thanks, it's fixed now! Hi again Bernhard, It looks like ports are building fine now. As I was building the first port on your system, I thought of an enhancement, and I am interested to know how difficult it would be to implement. I maintain various p5- and py- ports, and I often want to test them under multiple versions of Perl and Python, in case there are conditional behaviors in the Makefile. Assuming you're not planning on allowing users to create their own builds, what about adding the ability to set build variables in a make.conf file? For instance, if I commit etc/make.conf to my personal repository location, redports would overlay my options before starting the build. Then I could do things like force Python version 2.7, Perl version 5.10, etc. What do you think? That sounds a lot like OPTIONS support. Tinderbox is already able to do that so the only thing I need to solve are that it has to work in a shared environment. That means it will have to build all dependencies from scratch all the time because there are too many combinations and we don't really support mixing and matching weird combinations of slave ports (though everybody does it). Then add some user interface to enter contents of make.conf. OPTIONS support is already on my todo since the very beginning but I have no idea on when I will be able to work on 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: Zarafa port
On 05.02.2012 23:06, rfl...@acsalaska.net wrote: Hi, I've started working on a port of Zarafa, following http://wiki.freebsd.org/WantedPorts. I'm not sure if I can finish it, but I will try my bestest :). Zarafa has custom patches for libical and libvmime and this is why I have opted to create 2 supporting ports mail/zarafa-libvmime and devel/zarafa-libical. I was wondering if there are any objections to doing it that way or that they be somehow be merged with the original ports (difficult as specific versions are available at Zarafa's site to which the patches apply). For reference, I have attached the shar for the rough version of zarafa-libvmime, which currently misses CONFLICTS. -- Mel Thanks for starting to work on it! I've added a link from WantedPorts to that mail. Creating duplicate ports for special patches versions of a library is usually fine. We already have that in some cases where some ports depend on a specific version of a library. Some projects also ship modified versions of a dependency in their tree. Good examples for that are multimedia applications depending on ffmpeg. When they do a release their modified ffmpeg sources are included in their source tarball. If that is also the case for zarafa then don't create new ports for that but compile the libraries as part of the zarafa port. -- 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: xlocale support (Was: Re: Zarafa port)
On 07.02.2012 02:18, rfl...@acsalaska.net wrote: Hi, Thanks for starting to work on it! I've added a link from WantedPorts to that mail. Currently stuck on the absence of xlocale(3). Is there any chance these get MFC'd to RELENG_9 and RELENG_8? Or should I try implementing them in platform*.cpp within Zarafa? The latter looks possible, yet not trivial (still have to figure out what it needs from libc_private.h). Also open to workarounds or ports that implement these interfaces. It looks like xlocale support in current still has some problems so it needs to mature a bit more before it gets MFCd. Many projects have some fallback if xlocale.h does not exist and just need a small patch to don't include xlocale.h on FreeBSD. An example is the patch for multimedia/mlt: http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/mlt/files/patch-src__framework__mlt_property.h?rev=1.1 -- 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: Please test your commits
On 12.02.2012 22:43, Stephen Montgomery-Smith wrote: On 02/12/2012 03:33 PM, Andriy Gapon wrote: on 12/02/2012 23:22 Stephen Montgomery-Smith said the following: On 02/12/2012 03:15 PM, Andriy Gapon wrote: Today I became another user of redports.org. I can definitely recommend it. Yes, but it is not without its problems. I tried testing math/sage on redports.org. It reported an error building the dependency math/atlas, which built fine on mine and other people's systems. But still this is an instance of environment where the port can fail, so it warrants an investigation and fixing. Either in the port or in the redports infrastructure. Yes, you are correct. In fact, in the case of math/atlas there is the following report. It looks like people are working on it. http://portsmon.freebsd.org/portoverview.py?category=math&portname=atlas&wildcard= I think this isn't directly related. The build on redports had status "dud" in math/atlas which means the port has set IGNORE. I have no good way of telling which IGNORE line it is yet but it can only be one of: You have set WITH_ARCHDEF, but have not defined ARCHDEF You must select at least one of WITH_SHARED and WITH_STATIC both sound strange. Although, it also didn't work on report when I asked for an amd64 build. So it still didn't help me testing math/sage. I ended up relying on another user who politely informed me of build errors on his system, and was kind enough to try my patches. No objections from my side. You did the best you could and have some logfiles that prove that. So it is also a bit my fault for not implementing to show the exact IGNORE line but I have added it to my todo and will fix that. http://redports.org/buildarchive/20120208022438-13714/ Also, if everyone starts using it, isn't the backlog going to become huge? I'll let the redports team worry about this :-) Fair enough. A huge backlog is usually not a problem because there are build priorities and an somewhat intelligent scheduler so you won't end up waiting a day until the first build is finished. Also right now on very busy days the backend catches up during the night so build capacity is not too underpowered right now. I'm still working on getting more machines but that takes some time. -- 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: [CFT] Hadoop preliminary port
On 13.02.2012 09:48, Bleakwiser wrote: I was able to find some better information on the patch command through wikipeida, their article on it is really great. However I'm still not clear on what files I'm supposed to download to be running the patch on. I've dug around inside the .diff file with pico a bit and it's rather cryptic. Lots of things are commented (I assume by +) and I was also able to find some relevant man pages on 'patch' as opposed to 'man diff' i was using earlier. The correct command would be 'patch -p1 < hadoop-1.0.0.diff' not just 'patch -p1' w/o any other arguments, which tells the patch program to use the directory structure inside the .diff file. But perhaps piping the output of 'fetch' handles that all for me? However, we are getting way ahead of ourselves here and the same thing can be accomplished with different syntax. W/o having the correct software apply the patch to there isn't much sense in running the command at all anyway. Since I'm not familiar with the rather cryptic contents of .diff files I've wasted a good half hour just looking through it's contents for some clue as to exactly what I need to be downloading. Of course there is always the try and fail technique, where I would just simply try each tbz off the site and try and fail until it worked... for some reason I never liked that method. Thanks and again. I am defiantly not eleete enough to be helping test this port so I'll leave it to those informed already on the list. I wouldn't want to continue to waste anyone's time w/ trivial questions much less waste hours and hours of my own time looking up syntax for nitche CLI utilities so take care and good luck with the port. It's defiantly a 'killer app' so for BSD's sake I hope you folks get it. And as promiced, the /facepalm of failure... /facepalm There are at least 2 more ways to get hadoop. Clement has an redports.org account and is working on hadoop there. So you could just checkout his svn tree and get the latest port: 1) just fetch his redports.org repository compressed as tar.bz2: fetch http://redports.org/~clement/svn.tar.bz2 tar xvf svn.tar.bz2 2) you need devel/subversion installed for that svn co https://svn.redports.org/clement/ Now you need to manually add the hadoop lines in GIDs/UIDs to your /usr/ports/GIDs|UIDs files as well as copying over the devel/hadoop directory to /usr/ports. -- 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.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 10:26, Doug Barton wrote: On 02/22/2012 01:20, Andriy Gapon wrote: on 22/02/2012 05:40 Doug Barton said the following: On 02/21/2012 15:51, Andriy Gapon wrote: Could you please substitute the attached patch file for the corresponding file in the port and re-test the port? Good news, the kernel didn't panic. Bad news: supdrvGipCreate: failed to allocate the GIP page. rc=-8 vboxdrv: supdrvInitDevExt failed, rc=-8 module_register_init: MOD_LOAD (vboxdrv, 0xc66f33e0, 0) error 12 Yeah, I kind of expected something like this, because the original panic was in a memory allocation failure path. As to why the memory allocation fails I have no immediate insights. Maybe you genuinely don't have enough contiguous pages below 4GB boundary... It's i386, no PAE, so you could be on to something. I do have more than 4G in the box though: real memory = 6442450944 (6144 MB) avail memory = 3148255232 (3002 MB) Meanwhile, the 4.0 version worked on this same system ... The 4.0.16 version is still available as emulators/virtualbox-ose-legacy and doesn't include the memobj r0 patch so it should still work. (you will need to switch to devel/kBuild for 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: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 10:46, Doug Barton wrote: On 02/22/2012 01:41, Bernhard Froehlich wrote: The 4.0.16 version is still available as emulators/virtualbox-ose-legacy I know, that, but kind of beside the point, right? Yes, but some people depend on a working virtualbox and that is their safety net until the problem is sorted out. -- 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.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 21:07, Cy Schubert wrote: In message , Warren Block writ es: On Wed, 22 Feb 2012, Andriy Gapon wrote: > on 22/02/2012 11:26 Doug Barton said the following: >> Meanwhile, the 4.0 version worked on this same system ... > > The attached patched should try to grab the memory harder. No visible difference here, sorry. Same on my systems (8.2 and 9.0). My main server (9.0 dual core AMD X2) panics with a kernel page fault and hangs. My laptop (9.0 Penium-M) and my testbed (8.2 and 9.0 single core AMD X2) panic like my laptop, no messages, just an immediate reboot. (Something does flash up on the screen but it's there for milliseconds. We decided to backout the patch until this problem is solved. Commit was done a few minutes ago. -- 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: Porting "ispconfig"
On Wed, 22 Dec 2010 09:11:41 -0500, Jerry wrote: I was looking to see if there was a port for "ispconfig" <http://www.ispconfig.org/> in the ports system. I was not able to locate one. Assuming that one doesn't exist, is anyone working on porting this to FreeBSD? I've added ispconfig to the list of wanted ports. http://wiki.freebsd.org/WantedPorts -- 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: Xfce 4.8pre3
On Mon, 3 Jan 2011 22:49:32 +0100, Olivier Duchateau wrote: Hi, I don't know, if anyone follows development of Xfce 4.8, the next stable version comes out soon, scheduled on January 16th, 2011. There are still « things », that do not work well or are broken, in particular Thunar (thunar-volman is broken due to lack of udisks and gudev), and trash applet panel. I know that also miwi has done some work for xfce 4.8. He gave me his working directory for 4.8pre2 about 2 weeks ago. Probably that helps but don't ask me about the status or details of it. http://home.bluelife.at/patches/xfce48.tgz Wouldn't it be a good to talk to oliver@ first before duplicating all the work? How about creating a repository for Xfce ports like the ones that already exist for GNOME, KDE, Xorg, VirtualBox, Gecko, ... ? -- 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: xfce 4.8pre3 preview
On Thu, 13 Jan 2011 09:52:10 +0100, Oliver Lehmann wrote: The following ports are broken right now by the xfce upgrade and some of them will probably be marked as BROKEN or even IGNORE (thunar-volman for example) when 4.8 comes out: deskutils/orage Orage 4.8.0 has just been released. http://git.xfce.org/apps/orage Thanks for taking care of Xfce 4.8 :o) -- 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: Share SVN or something for people working on the ports together
On Sat, 22 Jan 2011 19:50:52 +0300, Subbsd wrote: > Hello. > > I think - maybe it's a good idea to create something like sourceforge place > but only for FreeBSD ports. A place online where some people can work > together for port, not individually as it is now. For example, I decided to > port libXXX on FreeBSD. One of the problem - i do not know -does over this > someone. So I created a project and start some work. No matter - can I > finish it or not - has registered and begun work. Other people see - cool, > someone has already started work on it. Once registered, they can also > correct or add to my work. This is to prevent a situation where a dozen > independent people start trying to port libXXX and everyone stumbles on its > own problems. Not all of us are professionals and have the same knowledge, > but work together more efficient. That's why it is always good to search first if someone has already worked on porting libXXX. Sometimes there is already a PR with a new port that just hasn't been committed yet or people stopped working on it at a specific build problem. Most of the time i see this happening with small ports that are not that much of work. For bigger projects I try to keep the wiki page http://wiki.freebsd.org/WantedPorts up to date. There you see the status of such a port and who is working on it. I won't cover all of them but I can always add more if people tell me. But it only makes sense if people know about that page and check it before starting to work on a bigger porting effort. -- 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 - unable to build in 8.1-STABLE
On Fri, 28 Jan 2011 16:47:13 +0300, Sergey Vinogradov wrote:
> Hi, everyone.
> Not sure, whether I should post this message here or in
> freebsd-emulation. Will post it here in the first place :)
> Recently I've stumbled into a problem with building
> emulators/virtualbox-ose. While making it crashed with the following
> message:
>
> kBuild: Installing tstVMStructRC
> =>
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/bin/tstVMStructRC
> kBuild: Generating tstVMStructSize
> -
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/bin/tstVMStructRC:
> 1: Syntax error: "(" unexpected kmk[2]: ***
> [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h]
> Error 2 kmk[2]: *** Deleting file
> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h'
> kmk[2]: *** Waiting for unfinished jobs kmk[2]: Leaving directory
That are the testcases and they seem to fail in rare and some very
specific situations. Could you try to build with DEBUG option enabled to
probably get a more verbose output? I'm not sure if it helps but that
output only tells me that there is a Syntax error in some file.
--
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: LIRC - Linux Infared Remote Control
On Fri, 18 Feb 2011 08:13:35 +0100, Lars Engels wrote: > On Thu, Feb 17, 2011 at 08:22:23PM -0500, grarpamp wrote: >> Putting 'infrared' into the search box here: >> http://www.freebsd.org/ports/ >> fails to list this port, because its description is spelled wrong. >> Daniel no longer maintains this. So I suppose the listing, long >> description, and Makefile contacts should be cut over to ports@. >> Thanks. > > Probably nox@ should step up? :) Yeah, don't worry. nox@ is working on updating the lirc port: http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-February/011636.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"
Call for Testers: VirtualBox 4.0.4
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 -- 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.0.4
On Sat, 19 Feb 2011 17:06:52 +0100, Olivier Smedts wrote: > 2011/2/19 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. > > I had to s/png.5/png.6/ and s/curl.5/curl.6/ in the Makefile of > emulators/virtualbox-ose, else it tried to install again png and curl. > My ports are all up-to-date. Don't know what you have done but the Makefile contains png.6 and curl.6. Please check again what you have downloaded and extracted. It seems to be wrong in a weird way. >>> > 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. > > Happens to me too : > ===> Installing for virtualbox-ose-4.0.4 > ===> Generating temporary packing list > ===> Checking if emulators/virtualbox-ose already installed > ===> Creating users and/or groups. > Using existing group `vboxusers'. > Creating user `vboxusers' with uid `920'. > pw: group `920' does not exist > *** Error code 67 > > I previously had virtualbox-ose-3.2.12 installed. I'm running > 9-CURRENT amd64. > > % grep vboxusers /etc/passwd > % grep vboxusers /etc/group > vboxusers:*:919:root,zozo > > Does it really needs a "vboxusers"
Re: Call for Testers: VirtualBox 4.0.4
On Fri, 18 Feb 2011 22:09:05 +0200, 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, >> Bernhard, on behalf of the FreeBSD Vbox Team >> > CONFLICTS missing for -kmod: > > laptop# pkg_info -xI virt > virtualbox-ose-4.0.4 A general-purpose full virtualizer for x86 hardware > virtualbox-ose-additions-4.0.4 VirtualBox additions for FreeBSD guests > virtualbox-ose-kmod-3.2.12_1 VirtualBox kernel module for FreeBSD > virtualbox-ose-kmod-4.0.4 VirtualBox kernel module for FreeBSD Thanks. Fixed in the repository in r1222 http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1222 -- 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: emulators/virtualbox-ose - unable to build in 8.1-STABLE
On Mon, 21 Feb 2011 19:31:05 +0300, Sergey Vinogradov wrote:
> В Fri, 28 Jan 2011 20:00:26 +0300
> Sergey Vinogradov пишет:
>
>> В Fri, 28 Jan 2011 16:11:47 +0100
>> Bernhard Froehlich пишет:
>>
>> > On Fri, 28 Jan 2011 16:47:13 +0300, Sergey Vinogradov wrote:
>> > > Hi, everyone.
>> > > Not sure, whether I should post this message here or in
>> > > freebsd-emulation. Will post it here in the first place :)
>> > > Recently I've stumbled into a problem with building
>> > > emulators/virtualbox-ose. While making it crashed with the
>> > > following message:
>> > >
>> > > kBuild: Installing tstVMStructRC
>> > > =>
>> > > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/bin/tstVMStructRC
>> > > kBuild: Generating tstVMStructSize
>> > > -
>> > > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h
>> > > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/bin/tstVMStructRC:
>> > > 1: Syntax error: "(" unexpected kmk[2]: ***
>> > > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h]
>> > > Error 2 kmk[2]: *** Deleting file
>> > > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h'
>> > > kmk[2]: *** Waiting for unfinished jobs kmk[2]: Leaving
>> > > directory
>> >
>> > That are the testcases and they seem to fail in rare and some very
>> > specific situations. Could you try to build with DEBUG option
>> > enabled to probably get a more verbose output? I'm not sure if it
>> > helps but that output only tells me that there is a Syntax error in
>> > some file.
>> >
>>
>> Ok, I've built it with DEBUG option turned on, here are the build
>> messages (I hope I've copypasted everything related to the problem):
>>
>> kBuild: Linking tstVMStructRC
>> Using built-in specs.
>> Target: amd64-undermydesk-freebsd
>> Configured with: FreeBSD/amd64 system compiler
>> Thread model: posix
>> gcc version 4.2.1 20070719 [FreeBSD]
>> /usr/bin/ld --eh-frame-hdr -m elf_i386_fbsd -V
>> -dynamic-linker /libexec/ld-elf.so.1
>> -o
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/obj/tstVMStructRC/tstVMStructRC
>> -L/usr/lib32 -L/usr/lib
>> -L/usr/lib
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/obj/tstVMStructRC/tstVMStructRC.o
>> /usr/lib32/crt1.o /usr/lib32/crti.o /usr/lib32/crtbegin.o
>> /usr/lib32/crtend.o /usr/lib32/crtn.o /usr/lib32/libc.so
>> GNU ld version 2.15 [FreeBSD] 2004-05-23 Supported emulations:
>> elf_i386_fbsd elf_x86_64_fbsd kBuild: Compiling tstAsmStructsasm
>> -
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/src/VBox/VMM/testcase/tstAsmStructsAsm.asm
>> kBuild: Linking tstGlobalConfig kBuild: Linking tstInstrEmul kBuild:
>> Linking tstVMM kBuild: Linking tstVMM-HwAccm
>> kBuild: Linking tstVMMFork
>> kBuild: Linking SUPInstall
>> kBuild: Linking SUPUninstall
>> kBuild: Linking SUPLoggerCtl
>> kBuild: Linking tstShflSizes
>> kBuild: Linking VBoxManage
>> kBuild: Linking VBoxHeadlessHardened
>> kBuild: Linking VBoxNetDHCPHardened
>> kBuild: Linking VBoxXPCOMIPCD
>> kBuild: Linking VBoxNetAdpCtl
>> kBuild: Linking VMMGC
>> kBuild: Linking VMMR0
>> kBuild: Linking VBoxDDR0
>> kBuild: Linking VBoxDD2R0
>> kBuild: Linking VBoxDDGC
>> kBuild: Linking VBoxDD2GC
>> kBuild: Installing scm
>> =>
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/bin/scm
>> kBuild: Installing VBoxSVC
>> =>
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/bin/VBoxSVC
>> kBuild: Installing tstVMStructRC
>> =>
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/bin/tstVMStructRC
>> kBuild: Generating tstVMStructSize
>> -
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/obj/VMM/tstVMStructRC.h
>> kBuild: Generating tstVMStructSize
>> -
>> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.2.12_OSE/out/freebsd.amd64/debug/obj/VMM/tstAsmStructsHC.h
>>
>> /usr/ports/emulators/virtualbox-o
Re: Call for Testers: VirtualBox 4.0.4
On Sat, 19 Feb 2011 07:59:27 +0100, Bernhard Fröhlich wrote: > >> 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. USB setup is documented in the wiki now. http://wiki.freebsd.org/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: FreeBSD needs fresh Blood!
On Wed, 9 Mar 2011 22:27:49 +0200, George Liaskos wrote: >> Building INDEX is not essential in this thread, merging trees is >> closer to subject, >> but primary I want, that testing development version of ports will be >> simpler. >> >> Please look at: 'Firefox 4 - Beta' threat: >> http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066353.html >> some people don't known where they can find freebsd-gecko development repo. >> >> Or at 'xorg-server 1.9.3 and 1.10.0' threat: >> http://lists.freebsd.org/pipermail/freebsd-ports/2011-March/066421.html >> Martin wrote: >>> I'll cleanup all the mess and commit all stuff to the xorg-dev repo. Maybe >>> someone have intressing to test it. >> but without any info where I can find xorg-dev repo, >> How I can test new xorg, since I don't known where this repo is? > > You can safely add gnome3, chromium and virtualbox to the list :p Actually virtualbox can be found in the blueports repository. http://svn.bluelife.at/index.cgi/blueports/view/README That repository started as a small svn repository for my own ports and currently has around 15 user accounts and is the home for some major ports like virtualbox, xbmc, mythtv, enna and cinelerra. It's main advantage currently is to have version control and an automatic tinderbox run on 7/8/9 on i386 and amd64 for each commit. But there are a few problems with it's current design and it's not really a sandbox but more like a ports tree of the hell. So I started a few weeks ago thinking and planning about how to do it right. It's a lot of work that is needed to be done on the tinderbox side and every user needs his own subtree and things like support for multiple tinderboxes and multiple architectures and a small wiki ... I plan to create a first prototype but due to lack of time it all takes very long. But it's important to mention that this is planned as a free infrastructure for everyone targeted at ports committers and ports maintainers. Why do i mention this here? Because I think it could be a very good infrastructure that can also include projects with teams and many ports like xorg or gecko in one place without having to recreate all the infrastructure for every project. Just to mention it - this is in no way a replacement for the FreeBSD ports tree. It's only for development ports. Thoughts? Wishes? -- 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"
Future direction of virtualbox-ose port on FreeBSD
Hi VirtualBox users. I'm sending this because there are a few problems in how we currently maintain the emulators/virtualbox-ose ports on FreeBSD. I want to outline my main concerns and propose a better way to solve that. The VirtualBox port is already very critical for many users and very complex at the same time so it gets harder and harder to update the port to new major versions without getting too much negative feedback from users. In the past we did a call for testers when upstream released a new major version (3.1.0, 3.2.0, 4.0.0) and got the update in the tree after their first patch release (3.1.2, 3.2.2) but now for the 4.0 release cycle we need at least to wait for 4.0.6 to get a useable state. Because of this long delay more and more people are using the cft and our development ports. We do not want that average users use that ports just to get to a newer version because they contain additional risks and are usually unstable versions (no support, irregular updates, broken ...). But we also do not want to make it harder for our testers to provide feedback because your feedback is very valuable to us and we need each tester we have. So we currently have these problems: 1) we need a stable version around if you hit a problem at the new version 2) we need to get new major versions out earlier to testers 3) we need to attract more testers We could solve this problems with "unstable" ports and people can use them if they care about it but we don't have that infrastructure in FreeBSD yet. We could also create -devel ports but that only solves one part of the problem and generates an huge amount of work on our side. Our internal -devel ports are most of the time built with "trunk" code so more or less alpha quality code. So that's not going to fly either. Instead we came up with two improvements: 1) Before a major version hits the tree we do a repocopy with the current version. So in case you have a problem with the major version you can fallback to the old version. It will be marked DEPRECATED with the next major update and removed 2 months after that. Major updates for vbox are 3.1.x, 3.2.x, 4.0.x 2) We provide binary packages and PBIs for virtualbox when we do a Call for Testers and probably also on a regular basis to lower the burden to test it. That only works for FreeBSD releases because the kernel module needs to be build for a specific kernel. So if you use a STABLE kernel you won't benefit from that. That means for us that we can bring in a new major version a bit earlier than now but we will continue to do extensive testing first. So you will still not see a .0 release in the ports. What do you think about it? Any better ideas? Your VirtualBox on FreeBSD Team, decke@, bapt@, (i. a. beat@) -- 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: Future direction of virtualbox-ose port on FreeBSD
On Wed, 13 Apr 2011 13:24:09 +0100, Bob Bishop wrote: > Hi, > > On 13 Apr 2011, at 12:38, Bernhard Froehlich wrote: > >> Hi VirtualBox users. >> >> I'm sending this because there are a few problems in how we currently >> maintain the emulators/virtualbox-ose ports on FreeBSD. [etc] > > A question: woud there be any advantage in separating out the kernel > module from the rest of it? Just asking, because I have no idea about > the stability of the components and interfaces. You mean a separate port for the kernel module? Yes, emulators/virtualbox-ose-kmod is exactly that. Sorry if I was not clear enough but everyone will be able to use the binary packages but if he has a STABLE kernel he will have to compile the corresponding -kmod port nevertheless. Using old kernel modules with newer VirtualBox versions is not supported (especially not between major versions which we are talking about here). -- 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-themes - why does it have a dependecy on mythtv-frontend?
On Mon, 18 Apr 2011 16:34:03 +0200, Torfinn Ingolfsen wrote: > Hi, > Question: why does multimedia/mythtv-themes have a dependecy on the > port multimedia/mythtv-frontend? > I have already installed multimedia/mythtv/, I do not need mythtv-frontend. > Details: > root@kg-quiet# uname -a > FreeBSD kg-quiet.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Apr 3 > 19:49:05 CEST 2011 > r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > root@kg-quiet# pv | grep mythtv > mythtv-0.24_1 = up-to-date with port > root@kg-quiet# pkg_info -W `which mythfrontend` > /usr/local/bin/mythfrontend was installed by package mythtv-0.24_1 mythfrontend binary is also provided from multimedia/mythtv so if you already have mythtv installed it should automatically take it. If you don't have any mythtv port installed it will default to multimedia/mythtv-frontend. -- 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: firefox crash - because of pthread_attr_setdetachstate
On Fri, 22 Apr 2011 11:12:48 +0400, Илья Ермолин wrote: > As I can see from settings PGO allready disabled Yeah, sorry have seen it too late. >From the stacktrace it looks like it's somewhere in the gnome area and someone with more knowledge about glib or pthread should check that line: GThread-ERROR **: file gthread-posix.c: line 340 (g_thread_create_posix_impl): error 'Invalid Argument' during 'pthread_attr_setdetachstate (&attr, joinable ? PTHREAD_CREATE_JOINABLE : PTHREAD_CREATE_DETACHED)' I've cc'd ports@ because there are a few more clever people. :o) -- Bernhard Froehlich http://www.bluelife.at/ > 2011/4/22 Bernhard Froehlich > >> On Fri, 22 Apr 2011 10:35:58 +0400, Илья Ермолин wrote: >> > Hi, >> > I have firefox4 builded from ports, but its crashes with strange >> back >> > trace... >> > >> > [cgi@free-cgi ~]$ firefox -g >> > /usr/local/lib/firefox/run-mozilla.sh -g >> /usr/local/lib/firefox/firefox-bin >> > MOZILLA_FIVE_HOME=/usr/local/lib/firefox >> > >> > >> > LD_LIBRARY_PATH=/usr/local/lib/firefox:/usr/local/lib/firefox/plugins:/usr/local/lib/firefox >> > DISPLAY=:0.0 >> > DYLD_LIBRARY_PATH=/usr/local/lib/firefox:/usr/local/lib/firefox >> > >> > >> > LIBRARY_PATH=/usr/local/lib/firefox:/usr/local/lib/firefox/components:/usr/local/lib/firefox >> > >> SHLIB_PATH=/usr/local/lib/firefox:/usr/local/lib/firefox >> > >> LIBPATH=/usr/local/lib/firefox:/usr/local/lib/firefox >> > ADDON_PATH=/usr/local/lib/firefox >> > MOZ_PROGRAM=/usr/local/lib/firefox/firefox-bin >> > MOZ_TOOLKIT= >> > moz_debug=1 >> > moz_debugger= >> > moz_debugger_args= >> > ddd: not found >> > /usr/bin/gdb --args /usr/local/lib/firefox/firefox-bin >> > GNU gdb 6.1.1 [FreeBSD] >> > Copyright 2004 Free Software Foundation, Inc. >> > GDB is free software, covered by the GNU General Public License, >> and you are >> > welcome to change it and/or distribute copies of it under certain >> > conditions. >> > Type "show copying" to see the conditions. >> > There is absolutely no warranty for GDB. Type "show warranty" >> for details. >> > This GDB was configured as "amd64-marcel-freebsd"... >> > (gdb) r >> > Starting program: /usr/local/lib/firefox/firefox-bin >> > [New LWP 100307] >> > [New Thread 809c041c0 (LWP 100307)] >> > >> > GThread-ERROR **: file gthread-posix.c: line 340 >> > (g_thread_create_posix_impl): error Недопустимый >> аргумент during >> > pthread_attr_setdetachstate (&attr, joinable ? >> PTHREAD_CREATE_JOINABLE : >> > PTHREAD_CREATE_DETACHED) >> > aborting... >> >>>>> Недопустимый аргумент - is Invalid >> Argument in translation from >> > Russian >> > >> > (gdb) bt >> > #0 0x0008063c6fcc in kill () from /lib/libc.so.7 >> > #1 0x0008063c5dcb in abort () from /lib/libc.so.7 >> > #2 0x0008057ccc05 in g_logv () from >> /usr/local/lib/libglib-2.0.so.0 >> > #3 0x0008057cced3 in g_log () from >> /usr/local/lib/libglib-2.0.so.0 >> > #4 0x00080567c184 in g_thread_create_posix_impl () >> > from /usr/local/lib/libgthread-2.0.so.0 >> > #5 0x0008057ea060 in g_thread_create_full () >> > from /usr/local/lib/libglib-2.0.so.0 >> > #6 0x000804f897e5 in g_dbus_proxy_get_cached_property_names >> () >> > from /usr/local/lib/libgio-2.0.so.0 >> > #7 0x000804f7b37c in g_dbus_connection_get_stream () >> > from /usr/local/lib/libgio-2.0.so.0 >> > #8 0x000804f775f7 in g_bus_get_sync () from >> > /usr/local/lib/libgio-2.0.so.0 >> > #9 0x00080bb4acbd in gconf_get_server () >> > from /usr/local/lib/libgconf-2.so.4 >> > #10 0x00080bb4af45 in gconf_activate_server () >> > from /usr/local/lib/libgconf-2.so.4 >> > #11 0x00080bb57924 in gconf_get_config_server () >> > from /usr/local/lib/libgconf-2.so.4 >> > #12 0x00080bb58434 in gconf_engine_connect () >> > from /usr/local/lib/libgconf-2.so.4 >> > #13 0x00080bb58639 in gconf_engine_get_database () >> > from /usr/local/lib/libgconf-2.so.4 >> > ---Type to continue, or q to quit--- >> > #14 0x00080bb58d37 in gconf_engine_notify_add () >> > from /usr/local/lib/libgconf-2.so.4 >> > #15 0x00080bb60bea in gc
Call for Testers: VirtualBox 4.0.6
It's about two months since the last call for testers and a lot of bugfixing has happened since then. Not all of the reported problems were FreeBSD related which is a good indication that we're not too far behind the stability of the other hosts. So let's get it one once again. Last time I asked for some help and Baptiste Daroussin (bapt@) made the classic mistake to respond. So all please welcome bapt to the FreeBSD Vbox Team! This is also the first time that we provide FreeBSD binary packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 platform and have the DEBUG option enabled. If you use a STABLE kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary package but have to compile the kernel module port for your kernel yourself. (emulators/virtualbox-ose-kmod) PBIs for PC-BSD are currently worked on and will hopefully be available in a few days. What has happened since the last cft: - VirtualBox update to 4.0.6 - phpvirtualbox updated to 4.0-5 - VIMAGE support added - vboxheadless startscript added - vboxwebsrv rc startscript fixes - Build fixed with LOCALBASE != PREFIX - Documentation of USB configuration (see pkg-message or Wiki) Thanks to all people that have contributed to that release and also reported problems for the last cft. We really appreciate that! Changes in the port: http://svn.bluelife.at/index.cgi/blueports/log/emulators Changelog for 4.0.6: http://www.virtualbox.org/wiki/Changelog FreeBSD specific configuration: http://wiki.freebsd.org/VirtualBox Todo List: http://wiki.freebsd.org/VirtualBox/ToDo Ports: http://home.bluelife.at/ports/virtualbox-cft-20110421.tar.gz FreeBSD 8.2/amd64 packages: virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz FreeBSD 8.2/i386 packages: virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz FreeBSD 7.4/amd64 packages: virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz FreeBSD 7.4/i386 packages: virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz Checksums: SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-amd64.tbz) = d7bdad02d2a04dd9dc3f12cc3ee002ce3bfc196b SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-i386.tbz) = e3023f5117fd15e918cba749d1ace2b7366bdc88 SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-amd64.tbz) = bd2785ac54e8363d217e35433d942ccae8bb7ffd SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-i386.tbz) = f6c437febf60828218cb42d7bfab8b536ecb7301 SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz) = 31bbe5ff1e8d9b14dbd64c5d1f964fb702efda9e SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz) = 019955d07293f25421a0ca49d67975c165ee3e85 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz) = e56736714e01dbe693515ed89e239337c7df77d3 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz) = 8f59294036b2f1ef407849f874139a80b6aabbcb SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz) = cc7e72fdcf0e2cd0bcd21bb152ffa8b1b1adcaae SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz) = be14e942cd2b426007b2d9a395cc65843340970d SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz) = d5be908e99f9dfc4f7a1efe1570b67ad2d6b8d27 SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz) = 2627acdb5ea9008bfa6ac6c2f452d6b883cfa40e SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz) = e846f4a94bf14d0a50d3deab0ae325da25e79448 SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz) = 68144054e11bebe21fcb2b19e99cb33cead6f25b SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz) = 7f08351028f18a3d76ed8c57aba525b11b47ee9a SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz) = 6e9bbfe0a2b19985b556e739f02f02a86ef873dd Mirrors: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/ (master) http://files.etoilebsd.net/vbox/4.0.6/ Thanks and good luck, Bernhard, on behalf of the FreeBSD Vbox 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.0.6 (PBIs now available)
On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: > PBIs for PC-BSD are currently worked on and will hopefully be available > in a few days. Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts to provide the PBIs! PC-BSD 8.x 32bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi PC-BSD 8.x 64bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi Feedback (positive and negative) from PC-BSD users is very welcome! -- 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.0.6
On Sun, 24 Apr 2011 16:37:15 -0400, Jason Andresen wrote: > On Fri, 22 Apr 2011 13:01:40 +0200 > Bernhard Froehlich wrote: > >> It's about two months since the last call for testers and a lot of >> bugfixing has happened since then. Not all of the reported problems were >> FreeBSD related which is a good indication that we're not too far behind >> the stability of the other hosts. So let's get it one once again. >> >> Last time I asked for some help and Baptiste Daroussin (bapt@) made the >> classic mistake to respond. So all please welcome bapt to the FreeBSD >> Vbox Team! > > Good news and bad news. The good news is that it appears to be > stable with my WinXP Pro VM. Bad news is that enabling 3D > acceleration still causes the VM to immediately crash when I try to > start it. Please try to get a coredump and stacktrace. You need to have the DEBUG option enabled or use the binary packages and set sysctl kern.sugid_coredump=1 first to also get coredumps for suid binaries like VirtualBox is. Once you have a core file please run "gdb /usr/local/lib/virtualbox/VirtualBox your_corefile.core" and send me the output of "bt full". -- 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.0.6 (PBIs now available)
On Sun, 24 Apr 2011 12:29:43 -0300, Sergio de Almeida Lenzi wrote: > For me it is working... > running windows XP dnd linux over an old(4.0.2) image it is ok... > very stable... > > Only a problem remains (that is not still fixed): > it is the problem with the vnc in VBoxHeadless > the cursor is not in sync (the vnc cursor) is not > in sync with the XP cursor.. although the sync > is better (compared with 4.0.2 but is still out of sync)... > How to reproduce: > VBoxHeadless --vnc --vncport 5901 --startvm XPimg > then goto another machine and execute: > vncviewer x.x.x.x:5901, the system opens works but the > mouse cursor is not in sync... > > Question: Will there be a fix??? Don't know if that is a bug or a problem of the implementation. I would recommend waiting for the VNC extpack. -- 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: VirtualBox 4.0.6 (PBIs now available)
On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote:
> On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich
> wrote:
>> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>>> PBIs for PC-BSD are currently worked on and will hopefully be available
>>> in a few days.
>>
>> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
>> to provide the PBIs!
>>
>> PC-BSD 8.x 32bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
>>
>> PC-BSD 8.x 64bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>>
>>
>> Feedback (positive and negative) from PC-BSD users is very welcome!
>>
>
> I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
> to start any virtual machines(both pre-existing VMs or a new VM that I
> tried to create). I get the following error dialog:
>
> Failed to open a session for the virtual machine RELENG_8_amd64.
>
> Failed to load VMMR0.r0
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Unknown error creating VM
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Details:
>
> Result Code:
> NS_ERROR_FAILURE (0x80004005)
> Component:
> Console
> Interface:
> IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
Yeah, thanks we already know. They added some strict hardening checks
in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently
rebuilding the PBIs with some modifications.
That's exactly why we have call for testers so find such weird problems
that nobody could think of.
--
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.0.6 (PBIs now available)
On Wed, 27 Apr 2011 15:28:11 -0400, Ryan Stone wrote:
> (Sorry for the noise earlier about the PBIs not working under PC-BSD;
> I'm not sure how I missed that had been already reported).
>
> I tried the new amd64 PBI and I am able to successfully start VMs now.
> I had one VM(running some relatively recent version of amd64 HEAD)
> boot up fine, but a second one (also running amd64 HEAD, but maybe a
> different svn revision) gets a Guru Meditation during startup. I'm
> not sure what is causing the crash. In their original configurations
> the working VM booted off of an emulated IDE disk while the broken VM
> booted of an emulated SATA disk, however I just tried changing the
> SATA disk to instead be an IDE disk and it doesn't seems to have
> resolved the problem.
>
> I'm not getting a corefile for the crash(or I'm unable to find it). I
> do have kern.sugid_coredump=1 and I'm running the PBI. Is this
> expected for a Guru Meditation, or should it be putting a core
> somewhere? I've put the VBox.log for the most recent crash here:
No, that looks fine.
> http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log
>
> This seems to be easy to reproduce so let me know if there's any more
> information that I can gather.
I've added it to the Todo list for 4.0.6 and will report it to the vbox
developers tomorrow. Sorry, don't have a clue what is going wrong there
- but i'm sure they know.
http://wiki.freebsd.org/VirtualBox/ToDo
> Also, the working VM was emulating uniprocessor machine. I tried
> adding a second CPU and that VM started crashing, too. I tried
> changing the broken VM to have only one core but it still crashes.
> I'm not sure if it's related to the first crash or not.
Look at the relevant parts of VBox.log and see if they look about the
same.
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current pointer
vs 84362000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current VMCS version e
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Entered Cpu 3
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current Cpu 2
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current pointer
vs 84365000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current VMCS version 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Entered Cpu 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current Cpu 0
00:00:08.374
!!
00:00:08.374 !!
00:00:08.374 !! Guru Meditation -4001
(VERR_VMX_INVALID_VMCS_PTR)
00:00:08.374 !!
00:00:08.374 !!
00:00:08.374 !! {mappings, }
00:00:08.374 !!
--
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.0.6
On Mon, 09 May 2011 05:57:05 -0700, Yuri wrote: > I think 4.0.6 is quite stable now. Is it really less stable than the > current version in ports 3.2.12? There are a few regressions also in 4.0.6 but it's already a lot better than 4.0.4. We have already decided last week to update the ports to 4.0.6 soon (currently waiting for a repocopy). > Why don't you at least put them into ports/emulators repository with > -devel suffix like many other ports do? So that there is no need to go > through the third party repository. Throwing another -devel port in the won't solve anything! In fact it would even make the situation much worse because it trains people to use beta software which we strongly discourage and causes even more error reports and debugging headaches for another version that we would have to maintain. We have that 3rd party repository because it is our working repository. You should not use it at all if you don't want to be a beta tester and work with us to solve specific problems. If you use them for regular systems you are clearly doing something wrong except you have done a _lot_ of testing. We know that the situation is not perfect and we have already taken a few actions to improve it but if that is still not enough to you we need more people and a bigger team to test earlier, more and faster. Read here: http://lists.freebsd.org/pipermail/freebsd-emulation/2011-April/008633.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.0.6
On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: > http://www.virtualbox.org/wiki/Changelog > 4.0.8 just released Don't you think we know that? http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 -- 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: VirtualBox 4.0.6
On Tue, 17 May 2011 22:31:56 +0800, Denny Lin wrote: > On Tue, May 17, 2011 at 10:34:44AM +0200, Bernhard Froehlich wrote: >> On Mon, 16 May 2011 23:45:08 -0700 (PDT), timp wrote: >> > http://www.virtualbox.org/wiki/Changelog >> > 4.0.8 just released >> >> Don't you think we know that? >> >> http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1316 > > Will this enter the ports tree soon? Yes, that's the plan. We're currently waiting for a repocopy to finish which will take at least a few more days and hope that 4.0.8 is not regressing too much. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156843 -- 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: VirtualBox 4.0.6
On Fri, 20 May 2011 09:58:35 +0200, Gour-Gadadhara Dasa wrote: > On Mon, 09 May 2011 07:30:41 -0700 > "Kevin Oberman" wrote: > >> 4.0.6 is still not as robust for me as 3.2.12, but it's now close and >> the added features still make it a win for me. I have not had an >> actual crash with 4.0.6, but I have had VMs simply deadlock. > > Does 4.0.x bring support for USB devices? Yes, but from the reports that we got I assume it only works with Windows XP guests right now. There are some bugs to fix. > I hope I might get my scanner working with VueScan which is not > possible via Linux-emulation. > > Will there be a 4.0.x port for 9.0 soon? Yes, hopefully pretty soon. -- 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: cannot launch VMs (upgrade to virtualbox-4.0.8)
On Sun, 22 May 2011 19:02:29 +0200, Gour-Gadadhara Dasa wrote:
> On Sun, 22 May 2011 18:04:33 +0200
> Gour-Gadadhara Dasa wrote:
>
>> Here is the error which I get:
>> http://imageshack.us/photo/my-images/43/vbox.png/ - It's
>> NS_ERROR_FAILURE (0x80004005).
>>
>> I saw some posts like this
>> http://forums.virtualbox.org/viewtopic.php?f=7&p=187733 but the
>> solution does not apply.
>
> After de-installing & re-installing virtualbox-ose-kmod, now I can
> launch my VMs again. :-)
Then you probably haven't restarted the machine after updating?
>>
>> Moreover, attempt to install Exension pack gives:
>>
>> "Failed to locate the main module ('VBoxPuelMain')"
>
> However, I still cannot install Extension pack. :-(
The PUEL Extpack is a binary blob that does not support FreeBSD. So
this is not supposed to work.
--
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: tt-rss
On Wed, 25 May 2011 19:37:21 -1000, Bruce Meier wrote:
> Hi,
>
> Had to add "define('PUBSUBHUBBUB_ENABLED', true);" to config.php to
> get update to work.
You _always_ need to merge the config.php with config.php-dist after an
update. They change it quite often also in patch releases. But there's
nothing the port can do for you.
--
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] Dolphin-emu preliminary port
On Tue, 19 Jul 2011 13:38:16 +0200, Ganael Laplanche wrote: > Hi everyone, > > I've been working on a dolphin (Wii/GC emulator) port, see : > > http://forums.dolphin-emulator.com/showthread.php?tid=8254 > > The emulator works on i386 with software rendering. > > Unfortunately, I can't get OpenGL rendering work on my laptop, > because of lack > of support for GL_EXT_framebufer_object. I would be glad to see if > some of you > can get it working. > > Amd64 support is not ready yet because of the lack of a MAP_32BIT flag for > mmap(2). I've tried a workaround, but without much luck (using MAP_FIXED). Dolphin is on our WantedPorts list so I've updated the entry with your infos. http://wiki.freebsd.org/WantedPorts -- 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] Hadoop preliminary port
On Mon, 8 Aug 2011 14:43:04 +0200, Clement Laforet wrote:
> On Mon, Aug 08, 2011 at 11:14:32AM +0200, Clement Laforet wrote:
>> Hi,
>>
>> You can find a preliminary port of hadoop 0.20.203.0 here:
>> http://people.freebsd.org/~clement/hadoop/
>
> Basic hive and pig ports are available here too.
>
> clem
>
>> Features:
>> - Hadoop user creation (UID: 950)
>> - basic rc scripts for all hadoop services
>> - native library build for current platform (i.e. 386 or amd64)
>> - bin/hadoop wrapper
>>
>> ToDo:
>> - Work on environment variables
>> - rc scripts clean up
>> - test test test
>> - install contrib
>> - install c++ stuff in ${PREFIX}
>>
>> All configuration files live in ${PREFIX}/etc/hadoop, log files in
>> /var/log/hadoop, and $HADOOP_HOME is ${PREFIX}/hadoop.
>>
>>
>> Thanks for your help,
>>
>> clem
Thanks a lot! Hadoop and Pig are on the
http://wiki.freebsd.org/WantedPorts so I've updated the status there.
--
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: cannot compile VirtualBox-ose 4.1.16 on FreeBSD 8.3-RELEASE amd64
On 31.05.2012 14:34, Miroslav Lachman wrote:
Hi,
I tried to install virtualbox-ose on our new testmachine, but
compilation ends with error:
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c:408:
error: expected '{' at end of input
kmk: ***
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o]
Error 1
The failing command:
@cc -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused -Wno-trigraphs
-fdiagnostics-show-option -Wno-long-long -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations
-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 -m64 -I/usr/include
-I/usr/X11R6/include -I/usr/local/include
-I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/include
-I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/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
-Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o.dep
-Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o
-Wp,-MP -o
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxAuth/pam/VBoxAuthPAM.o
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c
kmk: *** Waiting for unfinished jobs
kmk: *** Exiting with status 2
*** Error code 2
Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
Full output can be seen on http://pastebin.com/raw.php?i=7eDEWze8
The error above is completely unrelated because the problem starts much
earlier:
In file included from
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c:81:
/usr/include/security/pam_appl.h:43:35: error: security/openpam_attr.h:
No such file or directory
So it seems your system is broken. On my system I have the file and I
have just
checked that vbox 4.1.16 did build fine on a stock FreeBSD 8.3
Tinderbox.
# ident /usr/include/security/pam_appl.h
/usr/include/security/pam_appl.h:
$Id: pam_appl.h 408 2007-12-21 11:36:24Z des $
# uname -a
FreeBSD chii.bluelife.at 9.0-STABLE FreeBSD 9.0-STABLE #10: Wed May 23
23:30:26 CEST 2012
r...@chii.bluelife.at:/usr/obj/usr/src/sys/GENERIC amd64
--
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: cannot compile VirtualBox-ose 4.1.16 on FreeBSD 8.3-RELEASE amd64
On 01.06.2012 19:18, Miroslav Lachman wrote: Bernhard Froehlich wrote: On 31.05.2012 14:34, Miroslav Lachman wrote: Hi, I tried to install virtualbox-ose on our new testmachine, but compilation ends with error: [...] Full output can be seen on http://pastebin.com/raw.php?i=7eDEWze8 The error above is completely unrelated because the problem starts much earlier: In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/HostServices/auth/pam/VBoxAuthPAM.c:81: /usr/include/security/pam_appl.h:43:35: error: security/openpam_attr.h: No such file or directory So it seems your system is broken. On my system I have the file and I have just checked that vbox 4.1.16 did build fine on a stock FreeBSD 8.3 Tinderbox. # ident /usr/include/security/pam_appl.h /usr/include/security/pam_appl.h: $Id: pam_appl.h 408 2007-12-21 11:36:24Z des $ # uname -a FreeBSD chii.bluelife.at 9.0-STABLE FreeBSD 9.0-STABLE #10: Wed May 23 23:30:26 CEST 2012 r...@chii.bluelife.at:/usr/obj/usr/src/sys/GENERIC amd64 You are right! The system is missing /usr/include/security/openpam_attr.h - I don't know the reason. I successfully build VirtualBox on another machine. But there were some other problems: On one run, installation ends with: ===> Checking if emulators/virtualbox-ose already installed ===> Creating users and/or groups. Creating group 'vboxusers' with gid `920'. Creating user `vboxusers' with uid `920'. pw: user 'vboxusers' disappeared during update *** Error code 67 On the next run: ===> Checking if emulators/virtualbox-ose already installed ===> Creating users and/or groups. Using existing group `vboxusers'. Creating user `vboxusers' with uid `920'. pw: user 'vboxusers' already exists *** Error code 74 After few next runs (and manual deletion of the vboxusers) it was built and now I am running VirtualBox headless. So thank you very much for you time and work on VirtualBox! That is a symptom of a broken password database. So your password database /etc/pwd.db and /etc/master.passwd are out of sync and so pw complains. -- 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: cannot compile VirtualBox-ose 4.1.16 on FreeBSD 8.3-RELEASE amd64
On 01.06.2012 21:11, Miroslav Lachman wrote: Bernhard Froehlich wrote: On 01.06.2012 19:18, Miroslav Lachman wrote: Bernhard Froehlich wrote: On 31.05.2012 14:34, Miroslav Lachman wrote: [...] I successfully build VirtualBox on another machine. But there were some other problems: On one run, installation ends with: ===> Checking if emulators/virtualbox-ose already installed ===> Creating users and/or groups. Creating group 'vboxusers' with gid `920'. Creating user `vboxusers' with uid `920'. pw: user 'vboxusers' disappeared during update *** Error code 67 On the next run: ===> Checking if emulators/virtualbox-ose already installed ===> Creating users and/or groups. Using existing group `vboxusers'. Creating user `vboxusers' with uid `920'. pw: user 'vboxusers' already exists *** Error code 74 After few next runs (and manual deletion of the vboxusers) it was built and now I am running VirtualBox headless. So thank you very much for you time and work on VirtualBox! That is a symptom of a broken password database. So your password database /etc/pwd.db and /etc/master.passwd are out of sync and so pw complains. I think that pwd.db and master.passwd are OK. This error was shown on two different machines during the virtualbox-ose install. Just for the record. The virtualbox port only tells the ports framework that it needs some users/groups to install correctly by setting USERS= vboxusers but the actual creation of that happens within the ports framework (See create-users-groups target in /usr/ports/Mk/bsd.port.mk). So this has nothing to do with virtualbox itself - it just happens to be one of the ports that need a special user/group. Use pwd_mkdb(8) to recreate your password database and everything should be fine again. -- 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: New OPTIONS and make.conf knobs
On 04.06.2012 11:55, Miroslav Lachman wrote: There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose ===>>> Currently installed version: virtualbox-ose-4.1.16 ===>>> Port directory: /usr/ports/emulators/virtualbox-ose ===>>> This port is marked BROKEN ===>>> QT4 frontend requires X11 support. Run 'make config' again! ===>>> If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. That is not a bug at all. It was that way for the last 2 years and still is. The virtualbox ports do not use the new optionsng stuff yet and the problem that you are seeing is just because QT4 GUI without X11 doesn't make sense. If you don't want X11 you also don't want QT4. -- 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: New OPTIONS and make.conf knobs
On 04.06.2012 13:29, Miroslav Lachman wrote: Bernhard Froehlich wrote: On 04.06.2012 11:55, Miroslav Lachman wrote: There is another problem with options and portmaster. I have WITHOUT_X11=yes in make.conf and if I try to install emulators/virtualbox-ose for the first time it immediately ends with error message instead of showing options dialog. # portmaster emulators/virtualbox-ose ===>>> Currently installed version: virtualbox-ose-4.1.16 ===>>> Port directory: /usr/ports/emulators/virtualbox-ose ===>>> This port is marked BROKEN ===>>> QT4 frontend requires X11 support. Run 'make config' again! ===>>> If you are sure you can build it, remove the BROKEN line in the Makefile and try again. Terminated I don't know the order of processing options / knobs so I don't know if this is the problem of portmaster, OPTIONSng or Makefile it-self. To fix this problem, I must manually run `make config` in ports directory and uncheck QT4, then run portmaster again. That is not a bug at all. It was that way for the last 2 years and still is. The virtualbox ports do not use the new optionsng stuff yet and the problem that you are seeing is just because QT4 GUI without X11 doesn't make sense. If you don't want X11 you also don't want QT4. Yes, that's right. But I am confused why portmaster does not show the options dialog to let user uncheck QT4? What I expect is: - run portmaster - show dialog with unchecked X11 - let user uncheck QT4 - save options in /var/db/ports - show error about conflicting options Now is: - run portmaster - show error about conflicting options I don't know if it can be solved by portmaster, ports framework or anything else. From the BROKEN message: QT4 frontend requires X11 support. Run 'make config' again! I think it will be fixed once virtualbox uses optionsng because it is able to handle such option dependencies but for now it's the same as it ever was. -- 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"
VirtualBox on FreeBSD is looking for you!
Hi VirtualBox users! We are again at the point where I am kindly asking if someone is interested to help with the VirtualBox on FreeBSD work. We started with an active team of around 3 people but since about one year I ended up being a lonely ranger. Maintaining such a beast/high profile port by a single person is not possible for a longer period so we should really try to form a team to improve the situation. Additionally I started working on redports.org which requires more and more time so I cannot dedicate all my work to virtualbox. The situation of the port right now is not bad but I always end up fire fighting and only concentrate on serious problems due to the limited time I have. So it happens that people send bugreports and patches for virtualbox and don't get a response for weeks if at all. A lot of bugs that we have since day one are still present and the list of items that we should seriously do is getting longer. Many things of them are userland and porting stuff but there are also a lot of things to do in the kernel modules. Andriy Gapon has rewritten the r0 memory allocation stuff which significantly improved the situation in that area but the networking kernel modules are still in a bad shape. There are various known bugs (performance problems, instabilities, ...) in that area so it would be great if someone with networking expertise could have a look at the code. The USB stuff needs some love too. It is there but only works for a few special combinations of Device and Guest OS. Since VirtualBox 4.1 there is experimental support for PCI Passthrough so if we want that we need some Kernel API for the Intel/AMD IOMMU. I think the IOMMU code has already been written for BeHyVe so we need someone who puts all the stuff together and wants to find out how to integrate that in the kernel and vbox. The vbox developers offered their help on that but they need a Kernel API before we can start talking about it. So what is it that the virtualbox team needs to do? - regulary test latest SVN sources to find new problems early (build, runtime testing, create build fixes) - maintain all 8 ports (changes in CURRENT or other port updates keep breaking virtualbox around once per month) - update ports to new bugfix releases - review patches from the community and send them upstream then nag vbox developers to get them committed - help users to diagnose problems (help debugging, get stacktraces, collect information, give hints) - further porting efforts (coordinate and probably do it yourself) - optionsng adaptions - FreeBSD installer for the vbox additions to be able to build a VBoxAdditions.iso with FreeBSD support - implement vboxsf support (Shared Folders) - PCI Passthrough support - USB support (needs fixing) - Networking support (needs fixing) It is unrealistic that one single person can do a majority of these things so we seriously need a few people from different areas to improve the situation. Be it kernel developers, ports people or just power users that can help testing and diagnosing bugs. If you have an interest in VirtualBox on FreeBSD and a few spare cycles please get in contact with us (me?) to coordinate the further steps. I will do my best to help answering questions and help you with your first steps in vbox land. Don't worry if you think you are not experienced enough for the task. We all started that way and you get the chance to learn a lot - it just needs some time to get used to it. I have also created a dedicated VirtualBox on FreeBSD channel on freenode: #freebsd-vbox so you're welcome to join us! -- 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: MythTV 0.21 port upgrade
On Fri, 31 Oct 2008 16:05:16 -0400 Greg Larkin <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello everyone, > > I've been working on PR 126343 > (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343) to get > MythTV upgraded to 0.21 on FreeBSD. > > At the moment, I have a port that compiles cleanly, installs, starts > up the frontend and deinstalls correctly on 7.0. Of course, whether > it will actually record TV, playback, etc. is another matter > altogether. :) > > Is anyone out there willing to test out the port upgrade? I have a > mini-ITX PC here that could be set up for testing, but I need to get a > capture card first, unless MythTV will work with a USB capture dongle. > > In the mean time, I've placed the ports tree patch here: > > http://people.freebsd.org/~glarkin/diffs/mythtv-0.21.diff > > If you're game, download it, cd to the top of your ports tree and run: > > patch -E < /patch/download/dir/mythtv-0.21.diff > > You should then remove the *.orig files in the multimedia/mythtv/files > directory. > > Bug reports, port improvements and all feedback are welcome. I've > also adopted the port and hope to incorporate any suggestions sent my > way. Thats great! Have you seen ports/127856 ports/127857 and ports/128419? Because i have looked at your patch and it looks similar to the first PR but judging from the compile problems that got posted to this thread you're actually exactly where i was when writing the patches. PLEASE have a look at them because i see no sense in duplicating that work. When i think about the differences of you patch and ports/127856 i am not sure if there is anything that prevents it from working as a backend too. But i have no DVB-S card that is supported by FreeBSD so i cannot test it and only created a mythtv-frontend port which is actually working quite good for me. Runs perfectly fine with an mythbuntu backend. All that compile problems that were replied to this thread are already fixed as part of ports/127856. The reason is, that mythtv 0.21 uses a weird combination of ".." and "../.." in their include paths and so include libavcodec from /usr/local which is wrong because they have libavcodec included in their mythtv source package. -- 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 "[EMAIL PROTECTED]"
Re: amule 2.2.3 port - first try
Torfinn Ingolfsen gmail.com> writes: > > Hello, > I am updating the amule2 port to version 2.2.3, this is the first try. > The patch is attached. > There is (at least) one problem with the patch: it doesn't remove the > file ./files/patch-amuleDlg.cpp. For now, just remove the file > manually. > Doesn't FreeBSDs diff have an option to remove files? I read the ma > page but didn't find anything that looked useful. > > Testing: I have tested this patch on FreeBSD 7.1-prerelease / amd64, > and the amule 2.2.3 port compiles and installs fine. > > It would be nice if others coyld test the patch as well. > Feedback is welcome. 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've had a quick look over your patch and it seems to miss a few files. Have a look at ports-mgmt/porttools which is your swiss army knife as a porting guy. Sorry but i haven't found an english tutorial for it but i think a german one is also worth a look: http://www.chruetertee.ch/blog/archive/2008/05/03/freebsd-ports-mit-hilfe-von-porttools-erstellen-oder-aktualisieren.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"
