Re: PACKAGESITE spam
On Sun, 22 Dec 2013 15:48:49 +0400, Gleb Smirnoff wrote: Steve, On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S It did not ask how to stop this stupidity. I asked to have S this stupidity stopped by default. The spewing of this S information in /var/log/messages provides NOTHING. Please S turn it off by default. I am really suprised that someone might want to see this off by default. I concur. pkg info provides details of *currently installed* packages, whereas the information in syslog yields a *history*. This arrangement seems eminently reasonable to me. It all seems a bit of a storm in a teacup anyway, given that the logging can be directed to another file or turned off altogether, depending on requirements. My vote: Maintainers, thanks for your efforts and please keep it as it is. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10.0-RELEASE cycle status update
On Tue, 19 Nov 2013 11:22:05 -0500, Glen Barber wrote: As some may have noticed, the 10.0-RELEASE cycle has slipped a bit behind schedule. No worries; release it when it's ready. Many thanks to all concerned for their efforts. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Official FreeBSD Binary Packages now available for pkgng
On Sat, 02 Nov 2013 09:01:56 -0500, Eric van Gyzen wrote: On 11/02/2013 07:28 AM, Matthew Seaman wrote: I feel no obligation to do anything to encourage people that deliberately break the DNS. They've made their bed, and now they have to lie in it. Eric Camachat didn't break the DNS: his network administrator did. Matthew, you're right: that doesn't make sense. But people do it, often for security, either real or perceived. In this kind of environment, many other things are typically equally broken. I imagine Eric needs all the encouragement he can get. When Matthew mentioned people that deliberately break the DNS, I don't think he meant Eric personally; I think he was referring to Eric's *organisation*. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
libexecinfo?
We had a recent issue with libiconv now being included in base, thus rendering the port superfluous. Does a similar situation exist with libexecinfo? I don't seem to need the port on on 10.0-ALPHA1 r255587, and htop and ruby both build quite happily without it. The library is /usr/lib/libexecinfo.so.1. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: libexecinfo?
On Wed, 18 Sep 2013 19:11:50 +0200, Baptiste Daroussin wrote: On Wed, Sep 18, 2013 at 04:57:35PM +, Walter Hurry wrote: We had a recent issue with libiconv now being included in base, thus rendering the port superfluous. Does a similar situation exist with libexecinfo? I don't seem to need the port on on 10.0-ALPHA1 r255587, and htop and ruby both build quite happily without it. The library is /usr/lib/libexecinfo.so.1. libexecinfo in base is exactly the same as the on from ports, so it should be a change that doesn't require any manual operations. Ah, right. Thanks. Then I can safely do as I already have; i.e. remove the libexecinfo package and recompile those affected. This on the grounds that the fewer unnecessary ports the better, imho. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: dns/libidn puzzle
On Fri, 13 Sep 2013 02:44:57 +0200, Matthias Andree wrote: Am 12.09.2013 23:44, schrieb Walter Hurry: On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', I get a dialog asking me whether I want DOCS and/or NLS. However, on 10-CURRENT (r255358) I get this: $ cd /usr/ports/dns/libidn $ sudo make config === Options unchanged $ Why the difference? Is dialog4ports installed on your 10-CURRENT? Yes, it is. dialog4ports-0.1.5_1 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
dns/libidn puzzle
On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', I get a dialog asking me whether I want DOCS and/or NLS. However, on 10-CURRENT (r255358) I get this: $ cd /usr/ports/dns/libidn $ sudo make config === Options unchanged $ Why the difference? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Problem with virtualbox-ose-additions
I have upgraded to r255358, rebuilt world and kernel, and dealt with the iconv issues. In the process I had to delete a handful of ports, am now trying to reinstall them, and am running into a problem: FreeBSD freebsd.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r255358: Sat Sep 7 22:28:09 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM10 amd64 virtualbox-ose-additions will not compile. I get: kBuild: Linking VBoxOGLcrutil /usr/bin/ld: cannot find -liconv Have I done something wrong? How should I take this forward? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Problem with virtualbox-ose-additions
On Wed, 11 Sep 2013 00:20:09 +0200, Guido Falsi wrote: On 09/10/13 23:58, Walter Hurry wrote: I have upgraded to r255358, rebuilt world and kernel, and dealt with the iconv issues. In the process I had to delete a handful of ports, am now trying to reinstall them, and am running into a problem: FreeBSD freebsd.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r255358: Sat Sep 7 22:28:09 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM10 amd64 virtualbox-ose-additions will not compile. I get: kBuild: Linking VBoxOGLcrutil /usr/bin/ld: cannot find -liconv Have I done something wrong? How should I take this forward? This is another fallout from the iconv change. The port needs a fix. Most probably the same one applied to virtualbox-ose and virtualbox-ose-legacy. I'll commit a fix as soon as I have finished testing it. Thanks for the report. Success. Thanks very much for all your efforts and hard work. Much appreciated. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Ports with daemons on uninstall...
On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote: As long as this behavior only happens during pkg installs and never with ports, I'm OK. The worst is when a coworker forgets that the mysql port stops the daemon and my coworker upgrades with portmaster... the daemon is off the entire time mysql slowly compiles... I'm not familiar with portmaster, since I use portupgrade. That does the build first, then the deinstall old/install new. Seems a sensible approach anyway, in case the build fails. Doesn't portmaster work similarly? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Question about portsdb (part of ports-mgmt/portupgrade)
On 9.1-RELEASE, when I follow 'portsnap fetch update' with 'portsdb -u', it updates the INDEX-9 and INDEX-9.db files in /usr/ports for me. But the corresponding action doesn't happen on 10.0-CURRENT (r251572) until I do a 'portsdb -Fu'. Why the difference? Obviously it's no big deal, but I'm rather curious. This is portupgrade-2.4.10.5_1,2 in both cases, by the way. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can't compile lxpanel
On Fri, 07 Jun 2013 01:07:26 +0200, Dimitry Andric wrote: On Jun 6, 2013, at 18:21, Walter Hurry walterhu...@gmail.com wrote: On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote: Looks like a bug upstream. If this port worked in FreeBSD-9, then the difference might be the switch from gcc to clang. You could try compiling the port with gcc. Just add these lines to /etc/make.conf CC=gcc CXX=g++ CPP=gcpp Note: that will change the compiler used for ALL ports, as well as kernel and world. To selectively change the compiler for just a few ports, you can follow the examples here: http://www.freebsd.org/doc/en/articles/custom-gcc/article.html Thank you. Yes, switching to gcc (for that port only) worked. So should that go down as a defect in lxpanel, or in clang? It is a defect in lxpanel. The code is simply broken, as the error messages clearly show. Fixed now. Thanks go to the (new) maintainer. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Cannot startx on FreeBSD10 Current
On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote: From: Walter Hurry walterhu...@gmail.com Subject: Re: Cannot startx on FreeBSD10 Current Date: Fri, 14 Jun 2013 20:50:59 + (UTC) On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote: On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry walterhu...@gmail.com wrote: I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM. Recently, I started mentoring a Google Summer of Code student for the FreeBSD project. I worked with the student to set up a VM to run FreeBSD, with full graphical desktop. You might want to follow the instructions that the student followed here: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm- for- doing-gsoc-work/ Only interesting details: (1) Student used VMWare player instead of VirtualBox (shouldn't be a big deal). (2) We used pkgng to install binary packages (3) We used one of the pkgng mirrors, since pkgng packages from FreeBSD.org aren't fully available yet Other than that, things worked fine, and the student was able to get a full FreeBSD with graphical desktop inside a VM. Thanks for the pointer to the blog. With hindsight, it seems that your student avoided the issue I ran into by installing precompiled binaries, whereas I was using the Ports collection. The problem was the Clang miscompilation of xorg-server, as pointed out so kindly by Jung-uk Kim. Have you, or anybody else, sent a PR on this? I haven't. I don't know whether anyone else has. I used xorg-server with clang until recently. Now I'm on r249781. I think the problem started after the perl updates, but I might be wrong. Anyway, if nobody filed a PR yet, I'll do it. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Cannot startx on FreeBSD10 Current
I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM. Everything seems to work properly, except that I cannot 'startx'. All I get is a blank screen and an apparently hung box. The only way out of it is Machine - Close - Send the shutdown signal. The following appears in /var/log/Xorg.0.log: -- everything looks normal up to this point (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message. Fatal server error: AddScreen/ScreenInit failed for driver 0 Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. Segmentation fault at address 0x290 -- I don't know how to investigate this further. Any ideas? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Cannot startx on FreeBSD10 Current
On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote: I had the same issue the first time I've built Xorg, when I've first read: As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be needed to get GEM/KMS. See Intel_GPU https://wiki.freebsd.org/Intel_GPU for more details. at https://wiki.freebsd.org/Xorg I assume It worked out of the box just b installing Xorg... Intel_GPU https://wiki.freebsd.org/Intel_GPU page however pointed me to the right direction, which is: WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf. and then rebuild (portmaster -f for example) and it now starts. I still have some problems though... I can't switch to console with CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all nuts... the good thing is I can at least switch back to kde. I also noted that at shutdown/reboot I get a black screen nothing shows on screen, I just have to wait for it to turn off... I get the feeling that this is somehow related! Please note that I'm using a Acer S3 Ultrabook with a integrated Intel card... AMD info is here: https://wiki.freebsd.org/AMD_GPU Thanks for the reply. Well, this is in a VM, which reports the graphics adapter as: vgapci0@pci0:0:2:0: class=0x03 card=0x chip=0xbeef80ee rev=0x00 hdr=0x00 vendor = 'InnoTek Systemberatung GmbH' device = 'VirtualBox Graphics Adapter' class = display subclass = VGA When I put the two suggested enties into make.conf, xorg-server fails to compile, saying that it requires dri = 7.8, whereas my installed dri is 7.6.1_3,2 (from the Ports collection). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Cannot startx on FreeBSD10 Current
On Fri, 14 Jun 2013 18:20:32 +0200, Koop Mast wrote: On 14-6-2013 18:11, Walter Hurry wrote: On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote: I had the same issue the first time I've built Xorg, when I've first read: As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be needed to get GEM/KMS. See Intel_GPU https://wiki.freebsd.org/Intel_GPU for more details. at https://wiki.freebsd.org/Xorg I assume It worked out of the box just b installing Xorg... Intel_GPU https://wiki.freebsd.org/Intel_GPU page however pointed me to the right direction, which is: WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf. and then rebuild (portmaster -f for example) and it now starts. I still have some problems though... I can't switch to console with CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all nuts... the good thing is I can at least switch back to kde. I also noted that at shutdown/reboot I get a black screen nothing shows on screen, I just have to wait for it to turn off... I get the feeling that this is somehow related! Please note that I'm using a Acer S3 Ultrabook with a integrated Intel card... AMD info is here: https://wiki.freebsd.org/AMD_GPU Thanks for the reply. Well, this is in a VM, which reports the graphics adapter as: vgapci0@pci0:0:2:0: class=0x03 card=0x chip=0xbeef80ee rev=0x00 hdr=0x00 vendor = 'InnoTek Systemberatung GmbH' device = 'VirtualBox Graphics Adapter' class = display subclass = VGA When I put the two suggested enties into make.conf, xorg-server fails to compile, saying that it requires dri = 7.8, whereas my installed dri is 7.6.1_3,2 (from the Ports collection). You will need to run portmaster/portupgrade -a first to update your installed ports first. Mostly dri/libGL/libdrm. Did you know that the emulators/virtualbox-ose-additions port has xorg-server drivers for virtualbox video. Thanks, but my ports are fully up-to-date, and virtualbox-ose-additions is installed and running. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
SOLVED: Cannot startx on FreeBSD10 Current
On Fri, 14 Jun 2013 14:21:46 -0400, Jung-uk Kim wrote: I had a similar problem a week ago. Basically, that Clang version mis-compiles xorg-server. You may want to try the latest Clang on - -CURRENT or build it with make USE_GCC=any. Thenk you so much! Yes, recompiling xorg-server with gcc did the trick. Deeply appreciated. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Cannot startx on FreeBSD10 Current
On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote: On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry walterhu...@gmail.com wrote: I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM. Recently, I started mentoring a Google Summer of Code student for the FreeBSD project. I worked with the student to set up a VM to run FreeBSD, with full graphical desktop. You might want to follow the instructions that the student followed here: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for- doing-gsoc-work/ Only interesting details: (1) Student used VMWare player instead of VirtualBox (shouldn't be a big deal). (2) We used pkgng to install binary packages (3) We used one of the pkgng mirrors, since pkgng packages from FreeBSD.org aren't fully available yet Other than that, things worked fine, and the student was able to get a full FreeBSD with graphical desktop inside a VM. Thanks for the pointer to the blog. With hindsight, it seems that your student avoided the issue I ran into by installing precompiled binaries, whereas I was using the Ports collection. The problem was the Clang miscompilation of xorg-server, as pointed out so kindly by Jung-uk Kim. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can't compile lxpanel
On Fri, 07 Jun 2013 13:58:50 -0700, Jakub Lach wrote: Sorry for being so sparse, but I was just talking about general impression from few tries I gave it. /proc wasn't main problem, usually I didn;t have any use for it. Basically it wasn't for me what it aimed to be- a frugal replacement for DE. Half of things didn't work, other half worked erratically. Starting from bare panel/openbox looked more viable. OK, fair enough. All I can say is that LXDE works perfectly for me in 9.1- RELEASE. I just had the problem of compiling lxpanel in 10-CURRENT, which was worked around using asomers' suggestion to try gcc instead of clang for that port. Thanks for the reply. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can't compile lxpanel
On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote: Looks like a bug upstream. If this port worked in FreeBSD-9, then the difference might be the switch from gcc to clang. You could try compiling the port with gcc. Just add these lines to /etc/make.conf CC=gcc CXX=g++ CPP=gcpp Note: that will change the compiler used for ALL ports, as well as kernel and world. To selectively change the compiler for just a few ports, you can follow the examples here: http://www.freebsd.org/doc/en/articles/custom-gcc/article.html Thank you. Yes, switching to gcc (for that port only) worked. So should that go down as a defect in lxpanel, or in clang? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can't compile lxpanel
On Thu, 06 Jun 2013 08:37:10 -0700, Jakub Lach wrote: Last time I've checked lxde was unfortunately not worth hassle. e.g. it depends on /proc Sorry, I'm no expert, but is that a problem? I routinely mount proc on /proc in fstab. Is that what you are referring to? Is it undesirable to do so? Sorry to ask more questions, but I'd like to understand the issue. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Can't compile databases/py-sqlite3
On Tue, 04 Jun 2013 21:53:57 +0200, Dimitry Andric wrote: On Jun 4, 2013, at 21:15, Walter Hurry walterhu...@gmail.com wrote: I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. When I try a 'make install' in /usr/ports/databases/py-sqlite3 I get this very early on: === FreeBSD 10 autotools fix applied to /usr/ports/databases/py- sqlite3/work/Python-2.7.5/configure running config jemalloc: /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/ internal/arena.h:547: Failed assertion: binind NBINS || binind == BININD_INVALID *** Signal 6 Stop. make: stopped in /usr/ports/databases/py-sqlite3 I'm afraid this binind business doesn't mean much to me. Is there anything I can do? Please try the patch from this very recent post (on this very list ;-): http://lists.freebsd.org/pipermail/freebsd-current/2013-June/042230.html Yes, that has fixed my problem. Thank you very much. By the way. sorry for not spotting it in the other thread. I searched for 'sqlite3' before posting, but found nothing. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Can't compile lxpanel
I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. When I try to compile x11/lxpanel I get this: -- gmake[4]: Entering directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12/ src/plugins/volume' CC volume_la-volume.lo volume.c:193:20: error: non-void function 'on_button_press' should return a value [-Wreturn-type] if (! vol_spin) return; ^ volume.c:196:26: error: non-void function 'on_button_press' should return a value [-Wreturn-type] if (! vol_adjustment) return; ^ volume.c:217:19: error: non-void function 'on_button_press' should return a value [-Wreturn-type] if (! vol_spin) return; ^ volume.c:220:25: error: non-void function 'on_button_press' should return a value [-Wreturn-type] if (! vol_adjustment) return; ^ volume.c:286:21: error: non-void function 'volume_constructor' should return a value [-Wreturn-type] if (! vol_spin) return; ^ volume.c:289:27: error: non-void function 'volume_constructor' should return a value [-Wreturn-type] if (! vol_adjustment) return; ^ volume.c:309:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] PLUGINCLASS_VERSIONING, ^ ../../../src/plugin.h:35:5: note: expanded from macro 'PLUGINCLASS_VERSIONING' structure_size : sizeof(PluginClass), \ ^ volume.c:309:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] ../../../src/plugin.h:36:5: note: expanded from macro 'PLUGINCLASS_VERSIONING' structure_version : PLUGINCLASS_VERSION ^ volume.c:311:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] type : volume, ^~ .type = volume.c:312:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] name : N_(Volume Control), ^~ .name = volume.c:313:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] version: 1.0, ^~~~ .version = volume.c:314:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] description : Display and control volume, ^ .description = volume.c:316:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] constructor : volume_constructor, ^ .constructor = volume.c:317:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] destructor : volume_destructor, ^ .destructor = volume.c:318:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] config : NULL, ^~~~ .config = volume.c:319:5: warning: use of GNU old-style field designator extension [-Wgnu-designator] save : NULL ^~ .save = 10 warnings and 6 errors generated. gmake[4]: *** [volume_la-volume.lo] Error 1 gmake[4]: Leaving directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12/ src/plugins/volume' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12/ src/plugins' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12/ src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12' gmake: *** [all] Error 2 *** Error code 1 Stop. make: stopped in /usr/ports/x11/lxpanel *** Error code 1 Stop. make: stopped in /usr/ports/x11/lxpanel -- Is there anything I can do? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Can't compile databases/py-sqlite3
I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. When I try a 'make install' in /usr/ports/databases/py-sqlite3 I get this very early on: === FreeBSD 10 autotools fix applied to /usr/ports/databases/py- sqlite3/work/Python-2.7.5/configure running config jemalloc: /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/ internal/arena.h:547: Failed assertion: binind NBINS || binind == BININD_INVALID *** Signal 6 Stop. make: stopped in /usr/ports/databases/py-sqlite3 I'm afraid this binind business doesn't mean much to me. Is there anything I can do? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
