Re: Call for tester: VirtualBox 3.1.2 for FreeBSD
On Mon, Dec 28, 2009 at 10:04 AM, John Baldwin wrote: > On Monday 28 December 2009 9:25:28 am Gary Jennejohn wrote: [SNIP] >> >> Does vboxguest.ko have silent dependencies on other vbox modules? I only >> loaded vboxdrv.ko. > > Look in dmesg for the real kldload error message. > I'm seeing this as well: kernel: link_elf_obj: symbol _Z6strlenPKc undefined ...which, I suppose, is the real kldload error message. ___ 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 (take 2)
Working great here! I'm running it on a couple of notebooks and a desktop. Hosts: FreeBSD 9.0-CURRENT, FreeBSD 8.0-STABLE Guests: Windows XP SP3 32-bit Windows 7 32-bit PC-BSD 8.0 BETA (with virtualbox-ose-additions; video and mouse integration working properly) -Brandon ___ 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: fusefs-kmod on recent -current
On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil wrote: > Michael Butler wrote: > >> Seems that the change to the mount flags in recent -current has broken >> the compilation of sysutils/fusefs-kmod :-( >> >> It now needs something like the attached to compile, > > The attachment didn't make it. Anyway, there's already a PR about it: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/159322 > > Fabian > There are several patches actually: http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=&sort=none&text=fusefs-kmod&responsible=&multitext=&originator=&release= An appropriate one should be chosen that contains a check for the FreeBSD version. Getting the appropriate one committed seems to be the issue. Has anyone heard from this amis...@am-productions.biz? Can we get a manual override here? Main point of this simple-to-fix issue is that as 9.0-RELEASE approaches, having a broken fusefs-kmod is just bad news for a lot of users -- and it looks bad for FreeBSD too. -Brandon ___ 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: fusefs-kmod on recent -current
On Mon, Aug 29, 2011 at 6:50 PM, Anish Mistry wrote: > On Saturday 27 August 2011 22:28:08 Brandon Gooch wrote: >> On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil >> >> wrote: >> > Michael Butler wrote: >> >> Seems that the change to the mount flags in recent -current has >> >> broken the compilation of sysutils/fusefs-kmod :-( >> >> >> >> It now needs something like the attached to compile, >> > >> > The attachment didn't make it. Anyway, there's already a PR about >> > it: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/159322 >> > >> > Fabian >> >> There are several patches actually: >> >> http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&p >> riority=&class=&state=&sort=none&text=fusefs-kmod&responsible=&multit >> ext=&originator=&release= >> >> An appropriate one should be chosen that contains a check for the >> FreeBSD version. >> >> Getting the appropriate one committed seems to be the issue. Has >> anyone heard from this amis...@am-productions.biz? Can we get a >> manual override here? >> >> Main point of this simple-to-fix issue is that as 9.0-RELEASE >> approaches, having a broken fusefs-kmod is just bad news for a lot of >> users -- and it looks bad for FreeBSD too. > > Yes, please. I'm currently swamped and don't have the time to attend to > these. > > Thanks, > > -- > Anish Mistry > Excellent, thanks for replying Anish. Anyone know what the next step is? -Brandon ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Sep 27, 2011 10:04 AM, "Chris Rees" wrote: > > On 27 September 2011 10:18, Anton Shterenlikht wrote: > > On Tue, Sep 27, 2011 at 10:28:49AM +0200, O. Hartmann wrote: > >> On 09/27/11 08:35, h h wrote: > >> >Kevin Oberman writes: > >> > > >> >>On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: > >> >> > >> >>>With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be > >> >>>expected, ports/ is going to be essentially unusable for a while. > >> >>> > >> >>>The issue stems from configure scripts (to choose something completely > >> >>>at random) assuming that FreeBSD would never jump to a double-digit > >> >>>major version number, and as such, various regexps for "freebsd1*" (ie: > >> >>>FreeBSD 1.1.x) are now matching "freebsd10". > >> >[...] > >> >> > >> >>aDe, > >> >> > >> >>Could an entry to this effect be added to UPDATING (with a matching > >> >>entry when ports/ is "unbroken"). > >> > > >> >Also mention a workaround, e.g. > >> > > >> > $ export UNAME_r='9.9-BLAH' > >> > >> > >> Now I understand why some OS vendors have choosen the latin 10 'X' for > >> their tenth version of their operating system ... > > > > At least there will be a long rest after > > the move to 10 is complete.. until FreeBSD 100. > > > > > I'm afraid not; > > freebsd2*) > > We'll be just as screwed at 20. > > Hopefully we can fix that at the same time. > > Chris > Now is the moment we grab 'BSD', dropping the 'Free', and start fresh at a 1.x point... Rebrand and be more conservative with release numbering... Crazy right? Sorry for the noise... (Goes off to check the status of bsd.org) -Brandon ___ 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] Xorg 7.5.1
On Sat, Feb 19, 2011 at 7:25 AM, Martin Wilke wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Oy boys and gals, > > The Xorg T(m)eam is happy to announce the next round of Xorg fun! The X-Server > has been patched to the latest 1.7.X series, drivers and fonts have been > updated to the latest versions, but unfortunately we are not able to update > libGL, > drm and xorg-server to a higher version because FreeBSD doesn't support > GEM/KSE > (yet), but it looks good for now, as kib@ is working on that, so we hope the > future > will be better for us. This update includes some components from Xorg 7.6 > with a lot of > improvements, and it seems that the performance is much better than the old > version. > We are calling the update xorg 7.5.1. > > We hope you will enjoy the new stuff and give us a lot of feedback. We will > start an > exp-run tonight and depending on how much feedback we get, we plan to commit > this > update by the first weekend of March. A note for ATI users, the driver was > updated to > 6.14.0, so you may need to add some stuff to your xorg.conf in the "Section > "Device"" > > Option "int10" "on" > Option "BudType" "PCIE" > Option "RendrAccel" "on" > Option "AccelMethod" "exa" > Option "DynamicPM" "on" > Option "DRI" "on" > > So to get the xorg stuff you will need to: > > run > > svn co https://trillian.chruetertee.ch/svn/ports/branches/xorg-dev > > A small merge script to merge the svn checkout into the real portstree > can be found here: > > http://people.freebsd.org/~miwi/xorg/xorgmerge > > The script is a modified version of the kdemerge script. Please set the > KDEDIR variable to the path of your X.org ports. > > After merging, run one of the following command, depending on which tool > you use to manage your installed packages. > > portupgrade -a \* > portmaster -a > > Please report any problems and issues to x11 (at) FreeBSD.org. > > I would like to thank: > > Beat Gaetzi > Dima Panov > Koop Mast > Eitan Adler > > Without these people the Xorg update would still not be ready now. > > PS: Please don't send us mails with 'xorg update dosen't' work. > If you send us a report, please include the latest Xorg.conf > Xorg.log, uname -a output and pkg_info output. Thanks. > > Happy Updating! > > > - -- > +-oOO--(_)--OOo-+ > With best Regards, > Martin Wilke (miwi_(at)_FreeBSD.org) Working well here -- I see and "feel" noticeable improvement in screen drawing and interactivity with window items. Page scrolling in Firefox seems faster. Of course, it could be rather subjective :) An interesting thing as well, which I wasn't expecting: ACPI suspend/resume support has dramatically improved in speed and resilience. It takes just about a second for the display to come back on after resuming, where it would take between 3 to 5 seconds prior to the update. Cool :) A big "Thank You" to all of you! -Brandon ___ 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: Re: firefox 4 crashes after last nspluginwrapper-devel
On Thu, Mar 31, 2011 at 5:27 PM, Barbara wrote: > >>On Thursday 31 March 2011 02:34 am, Barbara wrote: >>> >On Wednesday 30 March 2011 07:03 pm, Barbara wrote: >>> >> I'm referring to this commit: >>> >> http://www.freebsd.org/cgi/getmsg.cgi?fetch=422486+0+current/cvs >>> >>-po rts >>> >> >>> >> After updating nspluginwrapper-devel, firefox instead of >>> >> randomly freezing for few seconds after closing o reloading a >>> >> tab with a flash running, crashes, which is even more annoying. >>> >> Now after the crash I have 2 core files: one for firefox-bin and >>> >> one for npviewer-bin. >>> >> Anyone else seeing the same? >>> > >>> >Did you reinstall libflashplugin.so wrapper in your >>> > ~/.mozilla/plugins directory? >>> > >>> >Just making sure... >>> > >>> >Jung-uk Kim >>> >>> I run "nspluginwrapper -a -v -i" in that directory, as I always did >>> after upgrading that port. >>> I think that you are talking about that, aren't you? >> >>Yes. I hardly use '-a', though. Can you please show me >>'nspluginwrapper -l' output? >> > > Sure! > $ nspluginwrapper -l > /home/bar/.mozilla/plugins/npwrapper.libflashplayer.so > Original plugin: /usr/local/lib/browser_plugins/libflashplayer.so > Plugin viewer: /usr/local/lib/nspluginwrapper/i386/linux/npviewer > Wrapper version string: 1.3.0 > > >>> I'd like to add that, from what I saw until now, the problem seems >>> happining only with FF4. >>> My "main" browser is www/seamonkey2 and I had no crash with it and >>> *it seems* (suggestion?not enough tests?) that the freezing >>> behaviour is gone. I think that Fedora still uses FF3.6.*, so maybe >>> the fix is good only for the pre-2 libxul/xulrunner/gecko engine, >>> maybe the glue part...?. Is that possible? >> >>Actually I myself use Firefox 4 on CURRENT/amd64 and I've never >>experienced such problem. > > I'm currently using it on 8_STABLE/i386. > >> Long ago, I had stale plugins around >>(i.e., accidentally ran 'nspluginwrapper -i' as root, which installed >>wrappers in system-wide location) and it caused such crash, though. >> > > I'm 100% sure I've never run it as root. > Do you think that rebuilding FF4 WITH_DEBUG could be of any help to understand > what's going on? > > Barbara I was running into the same issue with Firefox 4 crashing. When I built Firefox with debugging turned on, I couldn't get it to crash. So I don't think it will help in this scenario, but you could give it shot I suppose. I finally wound up removing and reinstalling Firefox, the linux compat layer (f10), the flash plugin, nspluginwrapper, and every trace of the plugin from my system (that I could find). I also followed the Handbook's recommended installation method, and began running "tests". The testing phase was simply opening many tabs with embedded flash objects :) So far, no crash. The only message I continue to see in the terminal from which Firefox is launched is: *** NSPlugin Wrapper *** ERROR: no valid NPP -> PluginInstance mapping found It doesn't seem to cause any real problems, so... Anyway, I'm going to keep hammering until something finally breaks, haha ^_^ -Brandon ___ 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: GNU make 3.82 update
On Sun, Apr 10, 2011 at 8:27 PM, Ade Lovett wrote: > Hi folks, > > After a few more -exp runs, we're down to exactly one piece of collateral > damage in terms of migrating from GNU make 3.81->3.82 > > It's a doozy. > http://tinderbox.lovett.com/errors/8.2-amd64-uxb/io-0.0.2009.08.03.log > > Apparently something is so messed up that a compiled interim binary fails to > run with 3.82 > > Since there's only this one port affected which in turn has one other > depending on it, I'm planning on committing the update tomorrow (April 11th) > and simply marking this port BROKEN. > > We will continue to have precisely one version of gmake in the tree -- > gmake381 will be nuked as part of the update and was only there to make > testing a bit easier. I believe someone owes me a beer on account of this. > > -aDe What port is it? Sorry, I can't determine from the previous message... Thanks for working on this! -Brandon ___ 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: GNU make 3.82 update
On Tue, Apr 12, 2011 at 1:57 AM, Sunpoet Po-Chuan Hsieh wrote: > On Tue, Apr 12, 2011 at 01:03:58AM -0500, Brandon Gooch wrote: >> On Sun, Apr 10, 2011 at 8:27 PM, Ade Lovett wrote: >> > Hi folks, >> > >> > After a few more -exp runs, we're down to exactly one piece of collateral >> > damage in terms of migrating from GNU make 3.81->3.82 >> > >> > It's a doozy. >> > ?http://tinderbox.lovett.com/errors/8.2-amd64-uxb/io-0.0.2009.08.03.log >> > >> > Apparently something is so messed up that a compiled interim binary fails >> > to run with 3.82 >> > >> > Since there's only this one port affected which in turn has one other >> > depending on it, I'm planning on committing the update tomorrow (April >> > 11th) and simply marking this port BROKEN. >> > >> > We will continue to have precisely one version of gmake in the tree -- >> > gmake381 will be nuked as part of the update and was only there to make >> > testing a bit easier. ?I believe someone owes me a beer on account of this. >> > >> > -aDe >> >> What port is it? Sorry, I can't determine from the previous message... >> >> Thanks for working on this! >> >> -Brandon > > Hi Brandon > > According to the tinerbox log URL, it's lang/io (io-0.0.2009.08.03). > And games/tnl depends on this port. > > -sunpoet > -- > Sunpoet Po-Chuan Hsieh > 4096R/CC57E36B 8AD8 68F2 7D2B 0A10 7E9B 8CC0 DC44 247E CC57 E36B > http://people.FreeBSD.org/~sunpoet/pgpkeys.txt Thanks! It's all so clear to me now ;) (I had thought that the 'io' in the log file name was indicative of some aspect of tinderbox...) -Brandon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Kernel Intel GPU driver and ports
On Sat, Jul 23, 2011 at 9:45 AM, Andriy Gapon wrote: > on 23/07/2011 16:51 Koop Mast said the following: >> svn co http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev > > svn: The OPTIONS response did not include the requested > activity-collection-set; > this often means that the URL is not WebDAV-enabled > > I am not an svn power user - is there anything I am doing wrong? > > -- > Andriy Gapon I think the repository is located here: svn co https://trillian.chruetertee.ch/svn/ports/branches/xorg-dev -Brandon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.2.4
On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich wrote: > Hi virtualbox users! > > This is again a call for testers to get some feedback before we commit > VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you > should definitely update to 4.2.4 because they fixed quite a few serious > bugs upstream. > > Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1 > is out the door. > > If you are interested in helping with virtualbox maintenance and > development or have noticed a bug you can easily find us on IRC. > > > Please update devel/kBuild-devel before updating any of the virtualbox > ports and ensure that your Kernel sources match your running kernel > before building the virtualbox-ose-kmod port. > > Changes since VirtualBox 4.1: > https://www.virtualbox.org/wiki/Changelog > > VirtualBox 4.2.4 and 4.1.22 (legacy) Ports: > http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz > > IRC: #freebsd-vbox on Freenode > > > Bernhard on behalf of the new VirtualBox on FreeBSD Team! > > -- > Bernhard Froehlich > http://www.bluelife.at/ I've updated to 4.2.4 on my system running HEAD. I've hit one annoying issue. I've been running the 4.2.0 Call for Testing for a while now, and it worked very well. After updating to 4.2.4 and updating the guest additions on several Linux guests, I've found that 3D acceleration is broken. The guest on which I didn't update the guest additions (so it's still running version 4.2.0 guest additions), 3D acceleration works great. This is a nuisance on systems which had some form of compositing enabled (e.g. compiz) because the login process (GDM in this case) just spins indefinitely waiting on (I presume) the window manager to fire up. Anyone else seeing this? -Brandon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.2.4
On Thu, Nov 8, 2012 at 8:12 AM, Bernhard Fröhlich wrote: > On Wed, Nov 7, 2012 at 4:21 AM, Brandon Gooch > wrote: >> On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich wrote: >>> Hi virtualbox users! >>> >>> This is again a call for testers to get some feedback before we commit >>> VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you >>> should definitely update to 4.2.4 because they fixed quite a few serious >>> bugs upstream. >>> >>> Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1 >>> is out the door. >>> >>> If you are interested in helping with virtualbox maintenance and >>> development or have noticed a bug you can easily find us on IRC. >>> >>> >>> Please update devel/kBuild-devel before updating any of the virtualbox >>> ports and ensure that your Kernel sources match your running kernel >>> before building the virtualbox-ose-kmod port. >>> >>> Changes since VirtualBox 4.1: >>> https://www.virtualbox.org/wiki/Changelog >>> >>> VirtualBox 4.2.4 and 4.1.22 (legacy) Ports: >>> http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz >>> >>> IRC: #freebsd-vbox on Freenode >>> >>> >>> Bernhard on behalf of the new VirtualBox on FreeBSD Team! >>> >>> -- >>> Bernhard Froehlich >>> http://www.bluelife.at/ >> >> I've updated to 4.2.4 on my system running HEAD. I've hit one annoying issue. >> >> I've been running the 4.2.0 Call for Testing for a while now, and it >> worked very well. >> >> After updating to 4.2.4 and updating the guest additions on several >> Linux guests, I've found that 3D acceleration is broken. The guest on >> which I didn't update the guest additions (so it's still running >> version 4.2.0 guest additions), 3D acceleration works great. >> >> This is a nuisance on systems which had some form of compositing >> enabled (e.g. compiz) because the login process (GDM in this case) >> just spins indefinitely waiting on (I presume) the window manager to >> fire up. >> >> Anyone else seeing this? > > Hm haven't checked that recently. The only thing that changed between 4.2.0 > and 4.2.2 from FreeBSD side was that we have enabled DRM in the additions > for FreeBSD guests but that should not affect Linux guests at all. > > I will check if I can reproduce that. > > -- > Bernhard Froehlich > http://www.bluelife.at/ I downgraded the guest additions from 4.2.4 to 4.2.0 and functionality is restored. This seems to be an issue with other host environments as well. Here's an example: https://forums.virtualbox.org/viewtopic.php?f=3&t=52215 -Brandon ___ 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: nvidia-driver broken by recent commit - 248084
On Sun, Mar 10, 2013 at 1:17 AM, AN wrote: > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #36 r248127: Sun Mar 10 > 00:13:59 CST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > /usr/ports/x11/nvidia-driver is broken, probably by this commit: > http://svnweb.freebsd.org/base?view=revision&revision=248084 > > From commit log:"The KPI results heavilly broken by this commit. Thirdy part > ports must be updated accordingly (I can think off-hand of VirtualBox, for > example)." > > > > root@FBSD10 /usr/ports/x11/nvidia-driver]# make clean > ===> Cleaning for nvidia-driver-310.32 > [root@FBSD10 /usr/ports/x11/nvidia-driver]# make install clean > ===> License NVIDIA accepted by the user > ===> Found saved configuration for nvidia-driver-304.64 > ===> nvidia-driver-310.32 depends on file: /usr/local/sbin/pkg - found > ===> Extracting for nvidia-driver-310.32 > => SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-310.32.tar.gz. > ===> Patching for nvidia-driver-310.32 > ===> Applying extra patch > /usr/ports/x11/nvidia-driver/files/r246085-patch-src-nvidia_linux.c > ===> nvidia-driver-310.32 depends on file: > /usr/local/libdata/pkgconfig/xorg-server.pc - found > ===> nvidia-driver-310.32 depends on shared library: GL.1 - found > ===> Configuring for nvidia-driver-310.32 > ===> Building for nvidia-driver-310.32 > ===> src (all) > @ -> /usr/src/sys > machine -> /usr/src/sys/amd64/include > x86 -> /usr/src/sys/x86/include > awk -f @/tools/makeobjops.awk @/kern/device_if.m -h > awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h > awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h > awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p > awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q > awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h > cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"310.32\" -D__KERNEL__ > -DNVRM -Wno-unused-function -Wuninitialized -O -mno-red-zone -mcmodel=kernel > -UDEBUG -U_DEBUG -DNDEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. > -I@ -I@/contrib/altq -fno-common -fno-omit-frame-pointer -mno-aes -mno-avx > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -c nvidia_ctl.c > In file included from nvidia_ctl.c:14: > In file included from ./nv-freebsd.h:77: > @/vm/vm_pager.h:127:2: error: implicit declaration of function 'rw_assert' is > invalid in C99 [-Werror,-Wimplicit-function-declaration] > VM_OBJECT_ASSERT_WLOCKED(object); > ^ > @/vm/vm_object.h:212:2: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' > rw_assert(&(object)->lock, RA_WLOCKED) > ^ > In file included from nvidia_ctl.c:14: > In file included from ./nv-freebsd.h:77: > @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED' > VM_OBJECT_ASSERT_WLOCKED(object); > ^ > @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' > rw_assert(&(object)->lock, RA_WLOCKED) >^ > In file included from nvidia_ctl.c:14: > In file included from ./nv-freebsd.h:77: > @/vm/vm_pager.h:144:2: error: use of undeclared identifier 'RA_WLOCKED' > VM_OBJECT_ASSERT_WLOCKED(object); > ^ > @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' > rw_assert(&(object)->lock, RA_WLOCKED) >^ > In file included from nvidia_ctl.c:14: > In file included from ./nv-freebsd.h:77: > @/vm/vm_pager.h:168:2: error: use of undeclared identifier 'RA_WLOCKED' > VM_OBJECT_ASSERT_WLOCKED(object); > ^ > @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' > rw_assert(&(object)->lock, RA_WLOCKED) >^ > In file included from nvidia_ctl.c:14: > In file included from ./nv-freebsd.h:77: > @/vm/vm_pager.h:191:2: error: use of undeclared identifier 'RA_WLOCKED' > VM_OBJECT_ASSERT_WLOCKED(m->object); > ^ > @/vm/vm_object.h:212:29: note: expanded from macro 'VM_OBJECT_ASSERT_WLOCKED' > rw_assert(&(object)->lock, RA_WLOCKED) >^ > 5 errors generated. > *** [nvidia_ctl.o] Error code 1 > > Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32/src. > *** [all] Error code 1 > > Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-310.32. > *** [do-build] Error code 1 > > Stop in /usr/ports/x11/nvidia-driver. > *** [install] Error code 1 > > Stop in /usr/ports/x11/nvidia-driver. > [root@FBSD10 /usr/ports/x11/nvidia-dr
Re: firefox build broken under clang 3.3
On Fri, Apr 19, 2013 at 1:06 PM, Florian Smeets wrote: > On 19.04.13 19:48, Dimitry Andric wrote: >> On Apr 19, 2013, at 17:56, Florian Smeets wrote: >> >>> On 19.04.13 04:01, kit wrote: updated current and now firefox and thunderbird both fail to build under the new clang 3.3. has anyone seen this or know how to fix? >>> >>> The fix is here: >>> >>> http://tb.smeets.im/~flo/gecko-clang33-fixes.diff >>> >>> It will be committed after the freeze. >> >> Are these fixes from upstream? If not, it would be nice to send them >> there... >> >> > > patch-bug854936 is a workaround because we don't have > http://llvm.org/viewvc/llvm-project?view=revision&revision=178950 yet. > > firefox-nightly (in our gecko svn repo) already compiles fine without > patch-clang33 > > So everything should be fine :) > > Florian Thanks for fixing the build issues. Now, I've built Firefox with Clang, but the darn thing segfaults at the drop of a hat: $ gdb /usr/local/bin/firefox firefox.core ... (gdb) bt #0 0x0008011eefaa in thr_kill () from /lib/libc.so.7 #1 0x0008024d254d in XRE_InstallX11ErrorHandler () from /usr/local/lib/firefox/libxul.so #2 0x000800f74116 in swapcontext () from /lib/libthr.so.3 #3 0x000800f73d39 in sigaction () from /lib/libthr.so.3 #4 0x7193 in ?? () #5 0x000800f73c20 in sigaction () from /lib/libthr.so.3 Previous frame inner to this frame (corrupt stack?) Rebuilding with debugging symbols provides no further insight, as that seems to provide a work-around for whatever the root cause may be (i.e. no more segfaults). Are any of you seeing something similar? -Brandon ___ 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 build broken under clang 3.3
On Tue, Apr 30, 2013 at 11:26 PM, Rafael Espíndola wrote: > This is now > > http://llvm.org/bugs/show_bug.cgi?id=15882 > > Someone familiar with the baseline compiler might be able to spot what > is wrong with the optimization. > > Cheers, > Rafael Just an FYI, I've been using firefox-21.0.b3,1 from: $ svn info Path: . Working Copy Root Path: /usr/home/brandon/wc/freebsd-gecko URL: https://trillian.chruetertee.ch/svn/freebsd-gecko/trunk/www/firefox Repository Root: https://trillian.chruetertee.ch/svn/freebsd-gecko Repository UUID: 6ab5617d-af29-de11-a9e3-001676731981 Revision: 1258 Node Kind: directory Schedule: normal Last Changed Author: jbeich Last Changed Rev: 1256 Last Changed Date: 2013-04-30 04:35:07 -0500 (Tue, 30 Apr 2013) I've not have a crash since. -Brandon ___ 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"
