devel/py-lxml fails to build on 10.0-CURRENT
Good day. I'm trying to build devel/py-lxml 2.3.2 (libreoffice dep) on 10.0-CURRENT with python27. Build fails like this: building 'lxml.etree' extension creating temp.freebsd-10.0-CURRENT-i386-2.7 creating temp.freebsd-10.0-CURRENT-i386-2.7/src creating temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.7 -c src/lxml/lxml.etree.c -o temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml/lxml.etree.o -w In file included from /usr/local/include/libxslt/xsltlocale.h:19, from /usr/local/include/libxslt/xsltInternals.h:24, from src/lxml/lxml.etree.c:265: /usr/include/xlocale.h:45: error: expected declaration specifiers or '...' before 'locale_t' Can anybody confirm that or it's just me? It builded just fine couple of weeks ago. Full buildlog here: http://people.freebsd.org/~rm/py-lxml.txt Thanks in advance. PS. I tried to rebuild libxslt/libxml2 to not avail. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: devel/py-lxml fails to build on 10.0-CURRENT
Yuri Pankov wrote on 16.12.2011 13:34: On Fri, Dec 16, 2011 at 01:17:41PM +0400, Ruslan Mahmatkhanov wrote: Good day. I'm trying to build devel/py-lxml 2.3.2 (libreoffice dep) on 10.0-CURRENT with python27. Build fails like this: building 'lxml.etree' extension creating temp.freebsd-10.0-CURRENT-i386-2.7 creating temp.freebsd-10.0-CURRENT-i386-2.7/src creating temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.7 -c src/lxml/lxml.etree.c -o temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml/lxml.etree.o -w In file included from /usr/local/include/libxslt/xsltlocale.h:19, from /usr/local/include/libxslt/xsltInternals.h:24, from src/lxml/lxml.etree.c:265: /usr/include/xlocale.h:45: error: expected declaration specifiers or '...' before 'locale_t' Can anybody confirm that or it's just me? It builded just fine couple of weeks ago. Full buildlog here: http://people.freebsd.org/~rm/py-lxml.txt Thanks in advance. PS. I tried to rebuild libxslt/libxml2 to not avail. Same here. Probably related: http://lists.freebsd.org/pipermail/svn-src-head/2011-November/031517.html Yuri Good catch, Yuri! Thank you. David, would you suggest anything wrt this breakage? If this an upstream issue what exactly should i tell to upstream about the reason that trigger this breakage? Thank you. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: devel/py-lxml fails to build on 10.0-CURRENT
В Fri, 16 Dec 2011 13:17:41 +0400 Ruslan Mahmatkhanov cvs-...@yandex.ru пишет: Good day. I'm trying to build devel/py-lxml 2.3.2 (libreoffice dep) on 10.0-CURRENT with python27. Build fails like this: building 'lxml.etree' extension creating temp.freebsd-10.0-CURRENT-i386-2.7 creating temp.freebsd-10.0-CURRENT-i386-2.7/src creating temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.7 -c src/lxml/lxml.etree.c -o temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml/lxml.etree.o -w In file included from /usr/local/include/libxslt/xsltlocale.h:19, from /usr/local/include/libxslt/xsltInternals.h:24, from src/lxml/lxml.etree.c:265: /usr/include/xlocale.h:45: error: expected declaration specifiers or '...' before 'locale_t' Can anybody confirm that or it's just me? It builded just fine couple of weeks ago. Full buildlog here: http://people.freebsd.org/~rm/py-lxml.txt Thanks in advance. PS. I tried to rebuild libxslt/libxml2 to not avail. I commented out #include xlocale.h in /usr/local/include/libxslt/xsltlocale.h And added #include xlocale.h in /usr/ports/devel/py-lxml/work/lxml-2.3.2/src/lxml/lxml.etree.c But this does not fix - it is only necessary for the successful building of the port... ___ 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: devel/py-lxml fails to build on 10.0-CURRENT
On Fri, Dec 16, 2011 at 01:17:41PM +0400, Ruslan Mahmatkhanov wrote: Good day. I'm trying to build devel/py-lxml 2.3.2 (libreoffice dep) on 10.0-CURRENT with python27. Build fails like this: building 'lxml.etree' extension creating temp.freebsd-10.0-CURRENT-i386-2.7 creating temp.freebsd-10.0-CURRENT-i386-2.7/src creating temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -O2 -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -I/usr/local/include/libxml2 -I/usr/local/include/python2.7 -c src/lxml/lxml.etree.c -o temp.freebsd-10.0-CURRENT-i386-2.7/src/lxml/lxml.etree.o -w In file included from /usr/local/include/libxslt/xsltlocale.h:19, from /usr/local/include/libxslt/xsltInternals.h:24, from src/lxml/lxml.etree.c:265: /usr/include/xlocale.h:45: error: expected declaration specifiers or '...' before 'locale_t' Can anybody confirm that or it's just me? It builded just fine couple of weeks ago. Full buildlog here: http://people.freebsd.org/~rm/py-lxml.txt Thanks in advance. PS. I tried to rebuild libxslt/libxml2 to not avail. Same here. Probably related: http://lists.freebsd.org/pipermail/svn-src-head/2011-November/031517.html Yuri pgpHD3OanEqPc.pgp Description: PGP signature
snort error install [bug report]
Hello! When I install snort-2.9.2 from the ports have a problem. See below (copy from shell): Making install in etc Making install in templates Making install in contrib Making install in rpm Making install in schemas Making install in m4 Making install in preproc_rules Making install in tools Making install in u2boat test -z /usr/local/bin || ../.././install-sh -c -d /usr/local/bin /bin/sh /usr/local/bin/libtool --mode=install install -s -o root -g wheel -m 555 u2boat '/usr/local/bin' libtool: install: install -o root -g wheel -m 555 -s u2boat /usr/local/bin/u2boat test -z /usr/local/share/doc/snort || ../.././install-sh -c -d /usr/local/share/doc/snort install -o root -g wheel -m 444 README.u2boat '/usr/local/share/doc/snort' Making install in u2spewfoo test -z /usr/local/bin || ../.././install-sh -c -d /usr/local/bin /bin/sh /usr/local/bin/libtool --mode=install install -s -o root -g wheel -m 555 u2spewfoo '/usr/local/bin' libtool: install: install -o root -g wheel -m 555 -s u2spewfoo /usr/local/bin/u2spewfoo test -z /usr/local/man/man8 || ./install-sh -c -d /usr/local/man/man8 install -o root -g wheel -m 444 snort.8 '/usr/local/man/man8' test -z /usr/local/lib/pkgconfig || ./install-sh -c -d /usr/local/lib/pkgconfig install -o root -g wheel -m 444 snort.pc '/usr/local/lib/pkgconfig' === Installing rc.d startup script(s) # mss: only doing this because snortsam patch/autojunk messes up paths # life is too short to figure out why. rmdir: /usr/local/lib/pkgconfig: Directory not empty *** Error code 1 Stop in /usr/ports/security/snort. *** Error code 1 Stop in /usr/ports/security/snort. --- Professional hosting for everyone - http://www.host.ru ___ 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: snort error install [bug report]
On Fri, Dec 16, 2011 at 04:47:04PM +0400, Alex wrote: Hello! When I install snort-2.9.2 from the ports have a problem. See below (copy from shell): Making install in etc Making install in templates Making install in contrib Making install in rpm Making install in schemas Making install in m4 Making install in preproc_rules Making install in tools Making install in u2boat test -z /usr/local/bin || ../.././install-sh -c -d /usr/local/bin /bin/sh /usr/local/bin/libtool --mode=install install -s -o root -g wheel -m 555 u2boat '/usr/local/bin' libtool: install: install -o root -g wheel -m 555 -s u2boat /usr/local/bin/u2boat test -z /usr/local/share/doc/snort || ../.././install-sh -c -d /usr/local/share/doc/snort install -o root -g wheel -m 444 README.u2boat '/usr/local/share/doc/snort' Making install in u2spewfoo test -z /usr/local/bin || ../.././install-sh -c -d /usr/local/bin /bin/sh /usr/local/bin/libtool --mode=install install -s -o root -g wheel -m 555 u2spewfoo '/usr/local/bin' libtool: install: install -o root -g wheel -m 555 -s u2spewfoo /usr/local/bin/u2spewfoo test -z /usr/local/man/man8 || ./install-sh -c -d /usr/local/man/man8 install -o root -g wheel -m 444 snort.8 '/usr/local/man/man8' test -z /usr/local/lib/pkgconfig || ./install-sh -c -d /usr/local/lib/pkgconfig install -o root -g wheel -m 444 snort.pc '/usr/local/lib/pkgconfig' === Installing rc.d startup script(s) # mss: only doing this because snortsam patch/autojunk messes up paths # life is too short to figure out why. rmdir: /usr/local/lib/pkgconfig: Directory not empty *** Error code 1 Stop in /usr/ports/security/snort. *** Error code 1 Stop in /usr/ports/security/snort. --- Professional hosting for everyone - http://www.host.ru This can be better addressed if you contact the maintainer directly, z...@freebsd.org Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpbpal1KdanA.pgp Description: PGP signature
Re: Fwd: Lousy timekeeping in VirtualBox 4.0.14
Hi! I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) box, and have a FreeBSD 10.0-CURRENT VM running underneath it. While the VM is running, it doesn't keep time worth a flip. This is even with the VirtualBox-Additions in it. 1) is this expected/known? I have seen similar behaviour on other systems (Linux+Qemu) and other versions of vbox+fbsd, so: I'm not surprised. From what I've heard, its a common virtualization issue. 2) What can we do to fix it? What diagnostics do you need? I *CAN* provide ssh access to both the host and the guest. I'd be willing to provide access to test hosts as well. -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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: A maintainers question: how to create a user?
--On December 15, 2011 7:16:09 PM -0500 Aryeh Friedman
aryeh.fried...@gmail.com wrote:
See subject for the main question... the details: I am the maintainer of
devel/aegis and the final installation step typically (linux RPM's for
example) is to create a user to hold the baselines (in svn/cvs/csup speak
the project's repo) of the varioous projects managed by aegis...
customerly this is MUST be a non-logginable (you MUST [requirements
document meaning of upper case MUST/SHOULD/MAY {NOT}) but allow for su
from either root or via sudo a member of wheel)... it is a standard
account in all other respects for example I typically set it to tcsh but
the port might want to make that an make time option... what is the best
way of setting this all up (both the no options and the options based
versions)
Look at USERS and GROUPS in /usr/ports/Mk/bsd.port.mk
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
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: Lousy timekeeping in VirtualBox 4.0.14
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/16/2011 9:54 AM, Maxim Khitrov wrote: On Thu, Dec 15, 2011 at 3:11 PM, Larry Rosenman l...@lerctr.org wrote: I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) box, and have a FreeBSD 10.0-CURRENT VM running underneath it. While the VM is running, it doesn't keep time worth a flip. This is even with the VirtualBox-Additions in it. 1) is this expected/known? 2) What can we do to fix it? What diagnostics do you need? I *CAN* provide ssh access to both the host and the guest. Did you try setting 'kern.hz=64' (or 100) in /boot/loader.conf for the guest? AFAIK, most clock issues in virtual machines have to do with missed interrupts, so reduce Kernel's timer frequency. - Max There is code in 10.0 to set it to 100, and that's what my guest is running. It seems to be when the host and the guest are all running full out, that the clock gets WAY off. I'm wondering if this is related to the sched_ule discussion. - -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO62pcAAoJENC8dtAvA1zmdh0H/jUZ4yRWLvvnt0Y6v8fI4X3t DgpE1gaK7s4JlqcUz1/GBQIraethSAxWidV39bggmVVl7Bj+8w0ZxwUOe+qWVLub YCKmWF60XnL/lsszDC9ej/K17hW8OTKVgdcZeepgoPIvr2wRB0gHU5O6NA95R3TO eKBjtE36gXTVTmK2gn/gKYtypOUSGkMi6RKaeiRKqZ/XLpYmSiUuwkkTcnZrhtuG 3BplWeJ/ltRIXuDuqaLmI73ssJWrmfHBKVFh4JE2XSe+R61dD/zKCKhBdxm6Ok2Z 3a9KNj7RgRPumOkv0ONF3vDumeoxOTrpIkebzYq4FCKyVyNnLf5E6tA+BMiFjiE= =bY5A -END PGP SIGNATURE- ___ 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: Lousy timekeeping in VirtualBox 4.0.14
On Thu, Dec 15, 2011 at 3:11 PM, Larry Rosenman l...@lerctr.org wrote: I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) box, and have a FreeBSD 10.0-CURRENT VM running underneath it. While the VM is running, it doesn't keep time worth a flip. This is even with the VirtualBox-Additions in it. 1) is this expected/known? 2) What can we do to fix it? What diagnostics do you need? I *CAN* provide ssh access to both the host and the guest. Did you try setting 'kern.hz=64' (or 100) in /boot/loader.conf for the guest? AFAIK, most clock issues in virtual machines have to do with missed interrupts, so reduce Kernel's timer frequency. - Max ___ 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: Lousy timekeeping in VirtualBox 4.0.14
On Thu, Dec 15, 2011 at 2:11 PM, Larry Rosenman l...@lerctr.org wrote: I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) box, and have a FreeBSD 10.0-CURRENT VM running underneath it. While the VM is running, it doesn't keep time worth a flip. This is even with the VirtualBox-Additions in it. 1) is this expected/known? 2) What can we do to fix it? What diagnostics do you need? I *CAN* provide ssh access to both the host and the guest. There is a bunch of tuning you can do with Virtualbox to try and alleviate such issues: http://www.virtualbox.org/manual/ch09.html#idp13756960 However no combination has worked for me. The only stable config I've been able to find is to setup NTP on host and guest and keep vboxservice running. Running vboxservice alone results in very erratic timekeeping and the service core dumps every few days. Running NTP alone results in the difference going too high and out of NTP's allowable range. -- Adam Vande More ___ 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
lang/gcc broken
Can someone please fix the lang/gcc port for FreeBSD-current? The weekly churn is lang/gcc46 gave me the brilliant idea to switch over to lang/gcc. What a $#@! nightmare! The only nightmare that surpasses the current lang/gcc fiasco is the questionable churn in lang/gcc46. -- Steve ___ 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: lang/gcc broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16/12/2011 17:51, Steve Kargl wrote: Can someone please fix the lang/gcc port for FreeBSD-current? The weekly churn is lang/gcc46 gave me the brilliant idea to switch over to lang/gcc. What a $#@! nightmare! The only nightmare that surpasses the current lang/gcc fiasco is the questionable churn in lang/gcc46. An error message would be helpful. Chris -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO64WwAAoJELCEktHh68rEdtUH/1X3qwZr+R5fg/8/8VAmYBXN Aqiluvc0K0NK+F5l6lafJ79iH2uy/F/ayiTEF+hdT55F4pF7oc7cy+t+7qRbyF1/ fxr85cepumPD1WlZnT8+T+HDRtR/gQp4znWZGtOtu4zcdMEZ+RlIghhNbgwos4NS KMBDsfdcl5w7uNfcsjtMR6n2/+XRNdWx9Bab5ngUrIDOZFgsrqrcsy/ZaUfP6Kco T9B7yu6b0AeC2KbBIMFezvZ/IlaApGZ8FwjHf6v3l11gXG8MqfdxCW9xfS4TSthX Vn0+QEcVjVsMcTPfF2t22vQlAocJHRUkLJHRP2IHjq4827Hiu2lAdxq2iCf29S4= =76rU -END PGP SIGNATURE- ___ 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: A maintainers question: how to create a user?
On 16 December 2011 15:27, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On December 15, 2011 7:16:09 PM -0500 Aryeh Friedman
aryeh.fried...@gmail.com wrote:
See subject for the main question... the details: I am the maintainer of
devel/aegis and the final installation step typically (linux RPM's for
example) is to create a user to hold the baselines (in svn/cvs/csup speak
the project's repo) of the varioous projects managed by aegis...
customerly this is MUST be a non-logginable (you MUST [requirements
document meaning of upper case MUST/SHOULD/MAY {NOT}) but allow for su
from either root or via sudo a member of wheel)... it is a standard
account in all other respects for example I typically set it to tcsh but
the port might want to make that an make time option... what is the best
way of setting this all up (both the no options and the options based
versions)
Look at USERS and GROUPS in /usr/ports/Mk/bsd.port.mk
It is possible to have aegis automatically added to wheel, but
personally I'd prefer that a message were printed to suggest that
rather than automate it Others may disagree!
Chris
___
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: Lousy timekeeping in VirtualBox 4.0.14
On Fri, Dec 16, 2011 at 10:04 AM, Adam Vande More amvandem...@gmail.com wrote: On Thu, Dec 15, 2011 at 2:11 PM, Larry Rosenman l...@lerctr.org wrote: I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) box, and have a FreeBSD 10.0-CURRENT VM running underneath it. While the VM is running, it doesn't keep time worth a flip. There is a bunch of tuning you can do with Virtualbox to try and alleviate such issues: http://www.virtualbox.org/manual/ch09.html#idp13756960 However no combination has worked for me. The only stable config I've been able to find is to setup NTP on host and guest and keep vboxservice running. Running vboxservice alone results in very erratic timekeeping and the service core dumps every few days. Running NTP alone results in the difference going too high and out of NTP's allowable range. I don't remember where I saw it, but have you tried to set the kernel tunable kern.hz=50 in your guest FreeBSD? It made a huge difference to me. -- llwang ___ 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
[PATCH] lang/gcc -- Fix build on freebsd-current
diff -ur gcc-4.6.2.orig/boehm-gc/configure gcc-4.6.2/boehm-gc/configure
--- gcc-4.6.2.orig/boehm-gc/configure 2011-10-26 02:30:24.0 -0700
+++ gcc-4.6.2/boehm-gc/configure2011-12-16 11:19:53.0 -0800
@@ -10520,7 +10520,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
@@ -12428,7 +12428,7 @@
esac
;;
- freebsd[12]*)
+ freebsd2*)
# C++ shared libraries reported to be fairly broken before
# switch to ELF
ld_shlibs_CXX=no
@@ -14203,7 +14203,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
diff -ur gcc-4.6.2.orig/configure gcc-4.6.2/configure
--- gcc-4.6.2.orig/configure2011-06-27 13:54:59.0 -0700
+++ gcc-4.6.2/configure 2011-12-16 11:19:03.0 -0800
@@ -3126,7 +3126,7 @@
noconfigdirs=$noconfigdirs sim target-rda
noconfigdirs=$noconfigdirs ${libgcj}
;;
- *-*-freebsd[12] | *-*-freebsd[12].* | *-*-freebsd*aout*)
+ *-*-freebsd2 | *-*-freebsd2.* | *-*-freebsd*aout*)
noconfigdirs=$noconfigdirs target-newlib target-libgloss ${libgcj}
;;
*-*-freebsd*)
diff -ur gcc-4.6.2.orig/gcc/config.gcc gcc-4.6.2/gcc/config.gcc
--- gcc-4.6.2.orig/gcc/config.gcc 2011-07-22 09:44:50.0 -0700
+++ gcc-4.6.2/gcc/config.gcc2011-12-16 11:19:24.0 -0800
@@ -272,7 +272,7 @@
| pdp11-*-bsd \
| sparc-hal-solaris2* \
| thumb-*-* \
- | *-*-freebsd[12] | *-*-freebsd[12].* \
+ | *-*-freebsd2 | *-*-freebsd2.* \
| *-*-freebsd*aout* \
| *-*-linux*aout* \
| *-*-linux*coff* \
diff -ur gcc-4.6.2.orig/gcc/configure gcc-4.6.2/gcc/configure
--- gcc-4.6.2.orig/gcc/configure2011-10-12 11:07:25.0 -0700
+++ gcc-4.6.2/gcc/configure 2011-12-16 11:19:40.0 -0800
@@ -16653,7 +16653,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
@@ -18537,7 +18537,7 @@
esac
;;
- freebsd[12]*)
+ freebsd2*)
# C++ shared libraries reported to be fairly broken before
# switch to ELF
ld_shlibs_CXX=no
@@ -20312,7 +20312,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
diff -ur gcc-4.6.2.orig/libffi/configure gcc-4.6.2/libffi/configure
--- gcc-4.6.2.orig/libffi/configure 2011-10-26 02:30:24.0 -0700
+++ gcc-4.6.2/libffi/configure 2011-12-16 11:16:32.0 -0800
@@ -9914,7 +9914,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
diff -ur gcc-4.6.2.orig/libgcc/config.host gcc-4.6.2/libgcc/config.host
--- gcc-4.6.2.orig/libgcc/config.host 2011-03-13 23:06:23.0 -0700
+++ gcc-4.6.2/libgcc/config.host2011-12-16 11:16:26.0 -0800
@@ -145,7 +145,7 @@
asm_hidden_op=.private_extern
tmake_file=t-darwin ${cpu_type}/t-darwin t-slibgcc-darwin
;;
-*-*-freebsd[12] | *-*-freebsd[12].* | *-*-freebsd*aout*)
+*-*-freebsd2 | *-*-freebsd2.* | *-*-freebsd*aout*)
# This is the place-holder for the generic a.out configuration
# of FreeBSD. No actual configuration resides here since
# there was only ever a bare-bones ix86 configuration for
diff -ur gcc-4.6.2.orig/libgfortran/configure gcc-4.6.2/libgfortran/configure
--- gcc-4.6.2.orig/libgfortran/configure2011-10-26 02:30:24.0
-0700
+++ gcc-4.6.2/libgfortran/configure 2011-12-16 11:17:48.0 -0800
@@ -11242,7 +11242,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
@@ -14870,7 +14870,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
diff -ur gcc-4.6.2.orig/libgo/configure gcc-4.6.2/libgo/configure
--- gcc-4.6.2.orig/libgo/configure 2011-02-20 20:17:20.0 -0800
+++ gcc-4.6.2/libgo/configure 2011-12-16 11:17:25.0 -0800
@@ -10046,7 +10046,7 @@
objformat=`/usr/bin/objformat`
else
case $host_os in
-freebsd[123]*) objformat=aout ;;
+freebsd[23]*) objformat=aout ;;
*) objformat=elf ;;
esac
fi
diff -ur gcc-4.6.2.orig/libgomp/configure gcc-4.6.2/libgomp/configure
--- gcc-4.6.2.orig/libgomp/configure2011-10-26
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. make_index: rubygem-chef-server-0.10.8: no entry for /usr/ports/sysutils/rubygem-chef-server-api make_index: rubygem-chef-server-0.10.8: no entry for /usr/ports/sysutils/rubygem-chef-server-webui Committers on the hook: joerg pgollucci Most recent CVS update was: U MOVED U devel/Makefile U devel/avr-binutils/Makefile U devel/avr-binutils/distinfo U devel/avr-binutils/pkg-descr U devel/avr-binutils/pkg-plist U devel/avr-binutils/files/patch-300-binutils-2.20.1-avr-size U devel/avr-binutils/files/patch-301-binutils-2.20.1-avr-coff U devel/avr-binutils/files/patch-302-binutils-2.20.1-new-sections U devel/avr-binutils/files/patch-303-binutils-2.20.1-as-dwarf U devel/avr-binutils/files/patch-304-binutils-2.20.1-dwarf2-AVRStudio-workaround U devel/avr-binutils/files/patch-305-binutils-2.20.1-assembler-options U devel/avr-binutils/files/patch-400-binutils-2.20.1-xmega U devel/avr-binutils/files/patch-401-binutils-2.20.1-new-devices U devel/avr-binutils/files/patch-402-binutils-2.20.1-avrtiny10 U devel/avr-binutils/files/patch-403-binutils-2.20.1-xmega128a1u-64a1u U devel/avr-binutils/files/patch-404-binutils-2.20.1-atxmega16x1-32x1 U devel/avr-binutils/files/patch-405-binutils-2.20.1-atxmega128b1 U devel/avr-binutils/files/patch-406-binutils-2.20.1-atxmega256a3bu U devel/avr-binutils/files/patch-407-binutils-2.20.1-at90pwm161 U devel/avr-binutils/files/patch-408-binutils-2.20.1-atmega16hvb-32hvb U devel/avr-binutils/files/patch-409-binutils-2.20.1-atmega32_5_50_90_pa U devel/avr-binutils/files/patch-410-binutils-2.20.1-attiny1634 U devel/avr-binutils/files/patch-411-binutils-2.20.1-atmega48pa U devel/avr-binutils/files/patch-500-binutils-2.20.1-bug13789 U devel/rubygem-dep_selector/Makefile U devel/rubygem-dep_selector/distinfo U devel/rubygem-dep_selector/pkg-descr U devel/rubygem-rake-compiler/Makefile U devel/rubygem-rake-compiler/distinfo U devel/rubygem-rake-compiler/pkg-descr U devel/rubygem-yajl-ruby077/Makefile U devel/rubygem-yajl-ruby077/distinfo U devel/rubygem-yajl-ruby077/pkg-descr U net/Makefile U net/rubygem-amqp067/Makefile U net/rubygem-amqp067/distinfo U net/rubygem-amqp067/pkg-descr U security/rubygem-net-ssh-multi/Makefile U security/rubygem-net-ssh-multi/distinfo U sysutils/Makefile U sysutils/rubygem-chef/Makefile U sysutils/rubygem-chef/distinfo U sysutils/rubygem-chef-expander/Makefile U sysutils/rubygem-chef-expander/distinfo U sysutils/rubygem-chef-expander/pkg-descr U sysutils/rubygem-chef-server/Makefile U sysutils/rubygem-chef-server/distinfo U sysutils/rubygem-chef-server/pkg-descr U sysutils/rubygem-chef-solr/Makefile U sysutils/rubygem-chef-solr/distinfo U sysutils/rubygem-chef-solr/pkg-descr U textproc/Makefile U textproc/rubygem-escape_utils/Makefile U textproc/rubygem-escape_utils/distinfo U textproc/rubygem-escape_utils/pkg-descr U textproc/rubygem-fast_xs/Makefile U textproc/rubygem-fast_xs/distinfo U textproc/rubygem-fast_xs/pkg-descr U www/Makefile U www/rubygem-chef-server-api/Makefile U www/rubygem-chef-server-api/distinfo U www/rubygem-chef-server-api/pkg-descr U www/rubygem-em-http-request/Makefile U www/rubygem-em-http-request/distinfo U www/rubygem-em-http-request/pkg-descr U www/rubygem-merb-assets/Makefile U www/rubygem-merb-assets/distinfo U www/rubygem-merb-assets/pkg-descr U www/rubygem-merb-core/Makefile U www/rubygem-merb-core/distinfo U www/rubygem-merb-core/pkg-descr U www/rubygem-merb-haml/Makefile U www/rubygem-merb-haml/distinfo U www/rubygem-merb-haml/pkg-descr U www/rubygem-merb-helpers/Makefile U www/rubygem-merb-helpers/distinfo U www/rubygem-merb-helpers/pkg-descr U www/rubygem-merb-param-protection/Makefile U www/rubygem-merb-param-protection/distinfo U www/rubygem-merb-param-protection/pkg-descr U www/rubygem-url_escape/Makefile U www/rubygem-url_escape/distinfo U www/rubygem-url_escape/pkg-descr ___ 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: [PATCH] lang/gcc -- Fix build on freebsd-current
Hi, Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? Cheers, -- Xin LI delp...@delphij.net https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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: INDEX build failed for 7.x
On 12/17/11 01:05, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. make_index: rubygem-chef-server-0.10.8: no entry for /usr/ports/sysutils/rubygem-chef-server-api make_index: rubygem-chef-server-0.10.8: no entry for /usr/ports/sysutils/rubygem-chef-server-webui I'm not sure whats up but I fixed at the same time I realized I forgot to add the webui port. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
Re: [PATCH] lang/gcc -- Fix build on freebsd-current
On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? My guess? We should rip out the [123] and [23] strings entirely. If anyone is running ports on FreeBSD 1, they have more problems than they can count right now. I can personally guarantee that ports don't work on 4.x (I ripped out the compat code several years ago that dealt with gross old make(1) bugs, etc.) and I think that means not 3.x either. In any case, the official claim is that the Ports Collection only supports 789 as first- class citizens right now, not anything older. mcl ___ 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: [PATCH] lang/gcc -- Fix build on freebsd-current
On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? There are probably a few different ways to workaround the problem. This is my 15 minute effort to get lang/gcc to build. gerald@ has indicated in another email thread that he'll probably backport GCC trunk's official patch. That's too much effort and too far out into the future for my immediate needs. -- Steve ___ 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: [PATCH] lang/gcc -- Fix build on freebsd-current
Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (gerald at FreeBSD.org) by the way? My guess? We should rip out the [123] and [23] strings entirely. If anyone is running ports on FreeBSD 1, they have more problems than they can count right now. I can personally guarantee that ports don't work on 4.x (I ripped out the compat code several years ago that dealt with gross old make(1) bugs, etc.) and I think that means not 3.x either. In any case, the official claim is that the Ports Collection only supports 789 as first- class citizens right now, not anything older. Fixes have already been implemented upstream, at Gerald's request, and are in lang/gcc46. But these fixes were introduced after the last stable release of gcc 4.6, which corresponds to lang/gcc. When a new version of gcc 4.6 is released, and the port is updated accordingly, it will include the fixes. In the meantime, I think Gerald was waiting for Martin to incorporate the patch to adjust the run-autotools-fixup target in ports/Mk/bsd.port.mk so that the target repairs ports like lang/gcc that use non-default *WRKSRC, by expanding the search in that target to WRKDIR. There hasn't been any further word on that for about a month-and-a-half -- presumably Martin is either busy with other work or is still trying to adjust the patch to fix some other problems. But you can make such a change on your own system. b. ___ 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: [PATCH] lang/gcc -- Fix build on freebsd-current
On Fri, Dec 16, 2011 at 09:15:06PM -0600, Mark Linimon wrote: On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? My guess? We should rip out the [123] and [23] strings entirely. If anyone is running ports on FreeBSD 1, they have more problems than they can count right now. I can personally guarantee that ports don't work on 4.x (I ripped out the compat code several years ago that dealt with gross old make(1) bugs, etc.) and I think that means not 3.x either. In any case, the official claim is that the Ports Collection only supports 789 as first- class citizens right now, not anything older. gerald@ has indicated that he'll do something with the official GCC way to deal with 1. versus 10. This patch is a stop gap for others, who like me, will run into a broken lang/gcc while we wait for a better solution. -- Steve ___ 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
INDEX now builds successfully on 7.x
___ 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
