Re: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]
On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich wrote: > I still think this is the wrong approach and I won't maintain all those > clang patches in the official port. The problem that I see is that we are > diverging from upstream vbox too much and end up maintaining a very special > usecase and a few dozen patches on our own. We would be the only one to > build with clang so with every release we need to update our patches and > add more to keep it building with clang. This will need someone that want's > to do it for the next few years. > > Since the beginning of vbox on FreeBSD we tried to stay close to upstream > sources and push patches to upstream first. This has worked good for us and > has created a good relationship to them. > > So we have 3 options: > > - I step down and wish you all the best. There are a few smart people > working on vbox now so it should not be an issue for the project. > > - Someone clones the vbox ports and maintains the clang version in the > portstree. > > - We try to push as many patches upstream and nag them until they accept > them. This might also interest some Mac OS X people. > > I will talk to the vbox developers to find out what they think of clang > and if someone is working on updating the recompiler from qemu which would > make a full clang build possible. > Well I hope that you don't have to leave the maintainership of the port. VirtualBox has a lot of dependencies, and it is very hard to keep everything on track and working, so I appreciate your efforts. I hope that VirtualBox upstream can accept our patches. -- Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]
On Sat, Jan 11, 2014 at 1:09 PM, Bernhard Fröhlich wrote: > > Am 11.01.2014 03:49 schrieb "Craig Rodrigues" : > > > (5) Build and install gsoap from jkim's port (you need to do this > because the version of gsoap in the ports tree will result in failed > compilation): > > > > cd /tmp/xy/jkim/devel/gsoap > > make > > make install > > Really? From what I was told the current gsoap should work fine with the > patch that he included for the new gsoap in his tree. > Yes, for some reason, when I tried to use the version of gsoap 2.8.10_2 in the ports tree, the build would fail when clang tried to compile certain gsoap-generated .cpp files. This was even with jkim's port Makefiles and patches. With the official virtualbox-ose port (not jkim's stuff), I also ran into compilation problems of gsoap files, but this time with gcc: http://lists.freebsd.org/pipermail/freebsd-emulation/2014-January/011203.html Upgrading the gsoap to the one in jkim's tree solved my problems building with clang. I did not try again with gcc. -- Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]
Am 11.01.2014 03:49 schrieb "Craig Rodrigues" : > > Hi, > > I had problems with the virtualbox-ose-4.22 port > under FreeBSD 10.0-RC5, where VirtualBox would occasionally > crash. > It looks like the mix of QT C++ libraries compiled with clang, > vs. the virtualbox-ose port compiled with g++46 was not a good mix I still think that this is a problem that needs to be fixed in Qt or even better in our ports tree. The decision to compile parts of the portstree with the base compiler and other parts with various compilers from ports is what causes all this issues. Hacking virtualbox cures the symptoms but does not fix the cause. > After reading this post: > http://lists.freebsd.org/pipermail/freebsd-emulation/2013-December/011171.html > > I obtained Jung-uk Kim's port Makefiles for VirtualBox and > I managed to compile a build of VirtualBox 4.3.6 on my system which is not > crashing. > > This is what I did: > > (1) Delete the virtualbox-ose port from my system: > > pkg delete virtualbox-ose > pkg delete virtualbox-ose-kmod > > (2) Delete the gsoap port from my system > > pkg delete gsoap > > (3) Make sure that a valid FreeBSD src tree exists under /usr/src, otherwise > the build will fail. > > (4) Check out jkim's tree from redports: > > mkdir -p /tmp/xy > cd /tmp/xy > svn co https://svn.redports.org/jkim > > (5) Build and install gsoap from jkim's port (you need to do this because the version of gsoap in the ports tree will result in failed compilation): > > cd /tmp/xy/jkim/devel/gsoap > make > make install Really? From what I was told the current gsoap should work fine with the patch that he included for the new gsoap in his tree. > (6) Build and install virtualbox-ose and virtualbox-ose-kmod ports. > > cd /tmp/xy/jkim/emulators/virtualbox-ose > make > make install > cd /tmp/xy/jkim/emulators/virtualbox-ose-kmod > make > make install That is the wrong order. You need to install kmod first or virtualbox will pull in kmod from the portstree in /usr/ports. > After doing this, I got a build of VirtualBox that: > -> built against clang, does not depend on g++ libraries > -> no need to unset QT_PLUGIN_PATH > -> works and doesn't crash :) > > Thank you for doing this Jung-uk, it was quite a lot of work > to port VirtualBox to clang! I still think this is the wrong approach and I won't maintain all those clang patches in the official port. The problem that I see is that we are diverging from upstream vbox too much and end up maintaining a very special usecase and a few dozen patches on our own. We would be the only one to build with clang so with every release we need to update our patches and add more to keep it building with clang. This will need someone that want's to do it for the next few years. Since the beginning of vbox on FreeBSD we tried to stay close to upstream sources and push patches to upstream first. This has worked good for us and has created a good relationship to them. So we have 3 options: - I step down and wish you all the best. There are a few smart people working on vbox now so it should not be an issue for the project. - Someone clones the vbox ports and maintains the clang version in the portstree. - We try to push as many patches upstream and nag them until they accept them. This might also interest some Mac OS X people. I will talk to the vbox developers to find out what they think of clang and if someone is working on updating the recompiler from qemu which would make a full clang build possible. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
clonehdd seems to hang.
I have been running this on a weekly basis for a while just to make sure I don't get caught out if a disk fails. For a few weeks now, it seems to run without completing. Here's where it seems to be right now. 74824 root 1 1190 3300K 1336K RUN 0 19.9H 100.00% dump I rotate between two disks on a weekly basis, as well. I added a second one to test if the disk I have been using is having trouble. But neither seems to be working. I'm also a little puzzled it would be cloning /tmp but not /etc if it's intended to yield a bootable clone drive. There doesn't seem to be a debug or verbose mode that tell me where it's having trouble. -- Paul Beard / www.paulbeard.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
On Sat, Jan 11, 2014 at 12:46 PM, Tijl Coosemans wrote: > The problem is pdftk-2.02. You need pdftk-2.02_1 for which a package > has been built already so it should be on the pkg mirrors soon. Bingo! That fixed the problem! Thank you!!! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Ports with duplicate LATEST_LINKs
On 01/11/14 10:39, Ports Index build wrote: > Dear port maintainers, > > The following list includes ports maintained by you that have duplicate > LATEST_LINK values. They should either be modified to use a unique > PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is > deprecated. See the portmgr blog post for more information: > http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ > > > Thanks, > Erwin "Annoying Reminder Guy III" Lansing > > > LATEST_LINK PORTNAME MAINTAINER > == > csound audio/csound po...@freebsd.org > csound audio/csound6 po...@freebsd.org Ooops! My fault!!! Sorry!!! > > Total: 2 ports > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Ports with duplicate LATEST_LINKs
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is deprecated. See the portmgr blog post for more information: http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ Thanks, Erwin "Annoying Reminder Guy III" Lansing LATEST_LINK PORTNAME MAINTAINER == csound audio/csound po...@freebsd.org csound audio/csound6 po...@freebsd.org Total: 2 ports ___ 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 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
On Sat, Jan 11, 2014 at 12:21 PM, Boris Samorodov wrote: > It's not a solution but a workaround which helped me. Run the following > command to find out which installed packages need gcc46 (note it's a > one line command): > - > % for o in `pkg info -aoq`; do \[ \! -z `pkg query %dn-%dv -o $o | grep > gcc46` \] && echo $o; done > - % sh $ for o in `pkg info -aoq`; do \[ \! -z `pkg query %dn-%dv -o $o | grep gcc46` \] && echo $o; done $ no results :-( > In my case opera and one more (may be virtualbox) packages used gcc46. > Just remove them, then remove gcc46 and upgrade packages. I did something different - I have removed both gcc and gcc46, then installed gcc46 to see what depends on it - result list empty - so it seems nothing on the port list depends on the lang/gcc46, the problem might be somewhere else..? Now when GCC is installed I cannot install GCC46. pkg clean does not help. Where did that GCC46 get from? :-) Thank you! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
On Sat, 11 Jan 2014 11:37:50 +0100 CeDeROM wrote: > On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote: >> On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote: >>> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of >>> doing USE_GCC? If so, here is the bug. > > Here goes the full ouput of the "pkg upgrade" maybe it will help you > find the solution :-) > > http://tny.cz/c8b678b2 The problem is pdftk-2.02. You need pdftk-2.02_1 for which a package has been built already so it should be on the pkg mirrors soon. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
11.01.2014 14:37, CeDeROM пишет: > On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote: >> On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote: >>> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing >>> USE_GCC? If so, here is the bug. >>> Gerald > > Here goes the full ouput of the "pkg upgrade" maybe it will help you > find the solution :-) > > http://tny.cz/c8b678b2 It's not a solution but a workaround which helped me. Run the following command to find out which installed packages need gcc46 (note it's a one line command): - % for o in `pkg info -aoq`; do \[ \! -z `pkg query %dn-%dv -o $o | grep gcc46` \] && echo $o; done - In my case opera and one more (may be virtualbox) packages used gcc46. Just remove them, then remove gcc46 and upgrade packages. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
On Sat, Jan 11, 2014 at 11:29 AM, CeDeROM wrote: > On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote: >> Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing >> USE_GCC? If so, here is the bug. >> Gerald Here goes the full ouput of the "pkg upgrade" maybe it will help you find the solution :-) http://tny.cz/c8b678b2 Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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 10.0-RC5 AMD64 pkg upgrade fail by gcc/gcc46
On Sat, Jan 11, 2014 at 3:18 AM, Gerald Pfeifer wrote: > Wait a minute: is one of yoir ports hard coding lang/gcc46 instead of doing > USE_GCC? If so, here is the bug. > Gerald Yes, it seems so, as I only installed packages from binaries and the gcc was the dependency, I did not install gcc46 by hand :-) After removing GCC and GCC46 still there is this conflict problem.. For the end-user it looks like packages upgrade fail with no apparent reason as there is "some" conflict :-) Thank you! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ biology/molden | 5.0.6 | 5.0.7 +-+ graphics/gphoto2| 2.4.14 | 2.5.3 +-+ graphics/libgphoto2 | 2.4.14 | 2.5.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
