Re: 10.0-CUR r226986 ports (general)
El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz escribió: Hello, I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November 1st; The ports/audio/jack seems installing fine, but the shared lib libjack.so is missing below ports/audio/jack/work and /usr/local/lib; it is mentioned in the list -L of the package; later ports/audio/arts and ports/x11/kde3 are missing the shared lib; It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as host_os: freebsd10.0 and the ./configure scripts have tests like this: ports/audio/jack/work/jack-audio-connection-kit-0.121.3: case $host_os in ... freebsd1*) dynamic_linker=no ;; ... And now? I'm cluesless now how we could solve this :-( matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: 10.0-CUR r226986 ports (general)
On 3 Nov 2011 06:11, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz escribió: Hello, I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November 1st; The ports/audio/jack seems installing fine, but the shared lib libjack.so is missing below ports/audio/jack/work and /usr/local/lib; it is mentioned in the list -L of the package; later ports/audio/arts and ports/x11/kde3 are missing the shared lib; It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as host_os: freebsd10.0 and the ./configure scripts have tests like this: ports/audio/jack/work/jack-audio-connection-kit-0.121.3: case $host_os in ... freebsd1*) dynamic_linker=no ;; ... And now? I'm cluesless now how we could solve this :-( Searching the archives of both these lists would help you ;) 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: dconf gconf wtfconf ?
On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: Can anyone explain the difference or need for both of these ? ports/devel/gconf -( Should'nt this be the only one needed ? ) ports/devel/dconf I just noticed dconf installed on my system. Well it is true that dconf is the replacement for gconf. It isn't a drop in replacement for gconf though. So both are needed. Both of these have the same WWW: of: http://www.gnome.org/projects/gconf/ I will have to fix the url for dconf, thanks. -Koop ___ 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: 10.0-CUR r226986 ports (general)
El día Thursday, November 03, 2011 a las 12:13:31PM +0100, Edward Tomasz Napierała escribió: It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as As a temporary workaround, add WITH_FBSD10_FIX=1 to /etc/make.conf. ports/UPDATING and some of the mails in the archive of -current recommend setting UNAME_r=9.0-CURRENT; is this the same or which method is prefered? Thanks matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: 10.0-CUR r226986 ports (general)
On Thu Nov 3 11, Matthias Apitz wrote: El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz escribió: Hello, I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November 1st; The ports/audio/jack seems installing fine, but the shared lib libjack.so is missing below ports/audio/jack/work and /usr/local/lib; it is mentioned in the list -L of the package; later ports/audio/arts and ports/x11/kde3 are missing the shared lib; It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as host_os: freebsd10.0 and the ./configure scripts have tests like this: ports/audio/jack/work/jack-audio-connection-kit-0.121.3: case $host_os in ... freebsd1*) dynamic_linker=no ;; ... And now? I'm cluesless now how we could solve this :-( are you sure this issue is related to the freebsd1* case? uname -a FreeBSD otaku 9.9-CURRENT FreeBSD 9.9-CURRENT #9: Thu Nov 3 11:41:08 CET 2011 arundel@otaku:/usr/obj/usr/git-freebsd-head/sys/ARUNDEL amd64 i did a 'cd /usr/ports/security/p11-kit ; make ; make install', yet from the following list: otaku% pkg_info -L p11-kit-0.8 Information for p11-kit-0.8: Files: /usr/local/bin/p11-kit /usr/local/include/p11-kit-1/p11-kit/p11-kit.h /usr/local/include/p11-kit-1/p11-kit/pin.h /usr/local/include/p11-kit-1/p11-kit/uri.h /usr/local/include/p11-kit-1/p11-kit/pkcs11.h /usr/local/lib/libp11-kit.a /usr/local/lib/libp11-kit.la /usr/local/lib/libp11-kit.so /usr/local/lib/libp11-kit.so.0 /usr/local/lib/p11-kit-proxy.so /usr/local/libdata/pkgconfig/p11-kit-1.pc /usr/local/share/gtk-doc/html/p11-kit/api-index-full.html /usr/local/share/gtk-doc/html/p11-kit/config-example.html /usr/local/share/gtk-doc/html/p11-kit/config-format.html /usr/local/share/gtk-doc/html/p11-kit/config-global.html /usr/local/share/gtk-doc/html/p11-kit/config-locations.html /usr/local/share/gtk-doc/html/p11-kit/config-module.html /usr/local/share/gtk-doc/html/p11-kit/config.html /usr/local/share/gtk-doc/html/p11-kit/gtk-doc.css /usr/local/share/gtk-doc/html/p11-kit/home.png /usr/local/share/gtk-doc/html/p11-kit/index.html /usr/local/share/gtk-doc/html/p11-kit/index.sgml /usr/local/share/gtk-doc/html/p11-kit/left.png /usr/local/share/gtk-doc/html/p11-kit/p11-kit-Future.html /usr/local/share/gtk-doc/html/p11-kit/p11-kit-Modules.html /usr/local/share/gtk-doc/html/p11-kit/p11-kit-PIN-Callbacks.html /usr/local/share/gtk-doc/html/p11-kit/p11-kit-URIs.html /usr/local/share/gtk-doc/html/p11-kit/p11-kit-Utilities.html /usr/local/share/gtk-doc/html/p11-kit/p11-kit.devhelp2 /usr/local/share/gtk-doc/html/p11-kit/up.png /usr/local/share/gtk-doc/html/p11-kit/reference.html /usr/local/share/gtk-doc/html/p11-kit/right.png /usr/local/share/gtk-doc/html/p11-kit/sharing-initialize.html /usr/local/share/gtk-doc/html/p11-kit/sharing-module.html /usr/local/share/gtk-doc/html/p11-kit/sharing.html /usr/local/share/gtk-doc/html/p11-kit/style.css /usr/local/share/examples/p11-kit/pkcs11.conf.example all *.so* files didn't get installed! cheers. alex matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: 10.0-CUR r226986 ports (general)
Wiadomość napisana przez Matthias Apitz w dniu 3 lis 2011, o godz. 07:10: El día Wednesday, November 02, 2011 a las 08:36:07PM +0100, Matthias Apitz escribió: Hello, I fetched 10-CUR from SVN as r226986 and /usr/ports from CVS on November 1st; The ports/audio/jack seems installing fine, but the shared lib libjack.so is missing below ports/audio/jack/work and /usr/local/lib; it is mentioned in the list -L of the package; later ports/audio/arts and ports/x11/kde3 are missing the shared lib; It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as As a temporary workaround, add WITH_FBSD10_FIX=1 to /etc/make.conf. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ 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: 10.0-CUR r226986 ports (general)
Wiadomość napisana przez Matthias Apitz w dniu 3 lis 2011, o godz. 12:26: El día Thursday, November 03, 2011 a las 12:13:31PM +0100, Edward Tomasz Napierała escribió: It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as As a temporary workaround, add WITH_FBSD10_FIX=1 to /etc/make.conf. ports/UPDATING and some of the mails in the archive of -current recommend setting UNAME_r=9.0-CURRENT; is this the same or which method is prefered? No, I guess UPDATING is right. It's just that I never remember to read it when encountering problems after an update, and the above method works for me. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ 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: 10.0-CUR r226986 ports (general)
El día Thursday, November 03, 2011 a las 11:28:47AM +, Alexander Best escribió: It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as host_os: freebsd10.0 and the ./configure scripts have tests like this: ports/audio/jack/work/jack-audio-connection-kit-0.121.3: case $host_os in ... freebsd1*) dynamic_linker=no ;; ... And now? I'm cluesless now how we could solve this :-( are you sure this issue is related to the freebsd1* case? I can only comment what I saw: - OS was detected as freebsd10.0 (I inserted a 'echo $host_os' into the ./configure script - ./configure said that it should/will not build shared libs - the *.so* were missing in ports/audio/jack/work/... and in /usr/local/lib I will remove all /usr/ports/* and /usr/local/* and /var/db/pkg/* and will start from scratch with cvs checkout and will set UNAME_r as explained in ports/UPDATING; will let you know the result matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: dconf gconf wtfconf ?
Koop Mast wrote on 03.11.2011 13:01: On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: Can anyone explain the difference or need for both of these ? ports/devel/gconf-( Should'nt this be the only one needed ? ) ports/devel/dconf I just noticed dconf installed on my system. Well it is true that dconf is the replacement for gconf. It isn't a drop in replacement for gconf though. So both are needed. Both of these have the same WWW: of: http://www.gnome.org/projects/gconf/ I will have to fix the url for dconf, thanks. -Koop Hi, Koop. Obviously pkg-descr of dconf should be fixed to not confuse people. Right now it's a duplicate of gconf2's pkg-descr. -- 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: 10.0-CUR r226986 ports (general)
On Thu Nov 3 11, Matthias Apitz wrote: El día Thursday, November 03, 2011 a las 11:28:47AM +, Alexander Best escribió: It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as host_os: freebsd10.0 and the ./configure scripts have tests like this: here's my config.log after building and installing security/p11-kit. i have edited my newvers.sh according to UPDATING and uname -a now properly reports: FreeBSD otaku 9.9-CURRENT FreeBSD 9.9-CURRENT #9: Thu Nov 3 11:41:08 CET 2011 arundel@otaku:/usr/obj/usr/git-freebsd-head/sys/ARUNDEL amd64 still for me the issue remains: no libs get built and thus not installed! cheers. alex ports/audio/jack/work/jack-audio-connection-kit-0.121.3: case $host_os in ... freebsd1*) dynamic_linker=no ;; ... And now? I'm cluesless now how we could solve this :-( are you sure this issue is related to the freebsd1* case? I can only comment what I saw: - OS was detected as freebsd10.0 (I inserted a 'echo $host_os' into the ./configure script - ./configure said that it should/will not build shared libs - the *.so* were missing in ports/audio/jack/work/... and in /usr/local/lib I will remove all /usr/ports/* and /usr/local/* and /var/db/pkg/* and will start from scratch with cvs checkout and will set UNAME_r as explained in ports/UPDATING; will let you know the result matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by p11-kit configure 0.8, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure --disable-gtk-doc --disable-nls --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd9.9 ## - ## ## Platform. ## ## - ## hostname = otaku uname -m = amd64 uname -r = 9.9-CURRENT uname -s = FreeBSD uname -v = FreeBSD 9.9-CURRENT #9: Thu Nov 3 11:41:08 CET 2011 arundel@otaku:/usr/obj/usr/git-freebsd-head/sys/ARUNDEL /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/local/diablo-jre1.6.0/bin ## --- ## ## Core tests. ## ## --- ## configure:2406: checking for a BSD-compatible install configure:2474: result: /usr/bin/install -c -o root -g wheel configure:2485: checking whether build environment is sane configure:2535: result: yes configure:2676: checking for a thread-safe mkdir -p configure:2715: result: ./install-sh -c -d configure:2728: checking for gawk configure:2758: result: no configure:2728: checking for mawk configure:2758: result: no configure:2728: checking for nawk configure:2744: found /usr/bin/nawk configure:2755: result: nawk configure:2766: checking whether make sets $(MAKE) configure:2788: result: yes configure:2868: checking whether build environment is sane configure:2918: result: yes configure:2921: checking whether to disable maintainer-specific portions of Makefiles configure:2930: result: yes configure:2986: checking build system type configure:3000: result: amd64-portbld-freebsd9.9 configure:3020: checking host system type configure:3033: result: amd64-portbld-freebsd9.9 configure:3074: checking how to print strings configure:3101: result: printf configure:3134: checking for style of include used by make configure:3162: result: GNU configure:3232: checking for gcc configure:3259: result: cc configure:3488: checking for C compiler version configure:3497: cc --version 5 cc (GCC) 4.2.2 20070831 prerelease [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3508: $? = 0 configure:3497: cc -v 5 Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.2 20070831 prerelease [FreeBSD] configure:3508: $? = 0 configure:3497: cc -V 5 cc: '-V' option must have argument configure:3508: $? = 1 configure:3497: cc -qversion 5 cc: unrecognized option '-qversion' cc: No input files specified configure:3508: $? = 1 configure:3528: checking whether the C compiler works configure:3550: cc -O2 -pipe -frename-registers
Re: dconf gconf wtfconf ?
On Thu, 2011-11-03 at 00:21 -0400, Jason Hellenthal wrote: Can anyone explain the difference or need for both of these ? ports/devel/gconf -( Should'nt this be the only one needed ? ) ports/devel/dconf I just noticed dconf installed on my system. Both of these have the same WWW: of: http://www.gnome.org/projects/gconf/ While dconf is a successor of gconf, it's not a drop-in replacement. Currently you need both. As a rule of thumb, Gnome2-era applications will be using gconf (some might keep using it for years to come,qq so gconf isn't going away), while most recent Gnome3-era applications already migrated, or are in the process of migration to dconf (note that even the base Gnome3 didn't yet fully moved to dconf as of Gnome 3.2) m. -- Michal Varga, Stonehenge (Gmail account) ___ 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: 10.0-CUR r226986 ports (general)
It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as As a temporary workaround, add WITH_FBSD10_FIX=1 to /etc/make.conf. ports/UPDATING and some of the mails in the archive of -current recommend setting UNAME_r=9.0-CURRENT; is this the same or which method is prefered? No, it is not the same. You can either masquerade, by setting UNAME_r and OSVERSION, or by editing the headers and scripts that define them; or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE). Right now the masquerading is probably safer, because there are some problems with the fix that are still being resolved -- and a few ports that may fail despite the fix. But of course if you help to test without masquerading, these problems will be resolved sooner. 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: 10.0-CUR r226986 ports (general)
Am 11/03/11 18:42, schrieb b. f.: It turns out that the problem is more general! A lot of ./configure scripts are detecting in 10-CUR that they can't or should not build shared libs; the problem is that the OS is detected now as As a temporary workaround, add WITH_FBSD10_FIX=1 to /etc/make.conf. ports/UPDATING and some of the mails in the archive of -current recommend setting UNAME_r=9.0-CURRENT; is this the same or which method is prefered? No, it is not the same. You can either masquerade, by setting UNAME_r and OSVERSION, or by editing the headers and scripts that define them; or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE). Right now the masquerading is probably safer, because there are some problems with the fix that are still being resolved -- and a few ports that may fail despite the fix. But of course if you help to test without masquerading, these problems will be resolved sooner. b. So I presume the WITH_FBSD10_FIX flag is set in /etc/make.conf, right? Setting this and try building ports without the masquerading will help those people involved in fixing more than the masquerading solution? If so, I would like to do so. I compile/update quite often ports, simply to keep my system fresh and for some testing purposes. At the moment I switch very often between CLANG and the legacy gcc 4.2.2 of FBSD 10, so it would not bother me much more as the inherited bothering due to the problems discussed if I have to switch one time more or prepare a PR for the problem. On the other hand, as far as I know, there was only suggested using UNAME_r. When do I have to use the OSVERSION? Regards Oliver signature.asc Description: OpenPGP digital signature
Re: 10.0-CUR r226986 ports (general)
On 11/3/11, O. Hartmann ohart...@zedat.fu-berlin.de wrote: Am 11/03/11 18:42, schrieb b. f.: So I presume the WITH_FBSD10_FIX flag is set in /etc/make.conf, right? You can set it in a number of local Makefiles that are automatically included during a port build. That includes make.conf, and the others mentioned in ports/Mk/bsd.port.mk. A few days ago Martin also added WITH_FBSD10_FIX to the Makefiles of a number of commonly-used ports that need the fix. Setting this and try building ports without the masquerading will help those people involved in fixing more than the masquerading solution? If Yes. Some of the known problems with the current fix don't occur when ports are built in tinderboxes or clean sandboxes, but on live systems that already have other ports installed. On the other hand, as far as I know, there was only suggested using UNAME_r. When do I have to use the OSVERSION? You don't have to alter OSVERSION, but if you do not, then for those ports that have WITH_FBSD10_FIX set in their Makefiles, the fix will be applied, and you will be subject to any problems that the fix may cause, even though you are trying to masquerade as a version of FreeBSD less than 10. Look at the conditional that determine whether any action is taken during the run-autotools-fixup target in ports/Mk/bsd.port.mk. 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: 10.0-CUR r226986 ports/net-mgmt/net-snmp
El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: No, it is not the same. You can either masquerade, by setting UNAME_r and OSVERSION, or by editing the headers and scripts that define them; or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE). Right now the masquerading is probably safer, because there are some problems with the fix that are still being resolved -- and a few ports that may fail despite the fix. But of course if you help to test without masquerading, these problems will be resolved sooner. Well, I will try to help. I have set WITH_FBSD10_FIX in /etc/make.conf; the port ports/net-mgmt/net-snmp installs: /usr/local/include/net-snmp/net-snmp-config.h with: ... /* define the system type include file here */ #define NETSNMP_SYSTEM_INCLUDE_FILE net-snmp/system/freebsd10.h ... but the named header file is not there: # ls -C1 /usr/local/include/net-snmp/system/free* /usr/local/include/net-snmp/system/freebsd.h /usr/local/include/net-snmp/system/freebsd2.h /usr/local/include/net-snmp/system/freebsd3.h /usr/local/include/net-snmp/system/freebsd4.h /usr/local/include/net-snmp/system/freebsd5.h /usr/local/include/net-snmp/system/freebsd6.h /usr/local/include/net-snmp/system/freebsd7.h /usr/local/include/net-snmp/system/freebsd8.h /usr/local/include/net-snmp/system/freebsd9.h I don't know what the correct fix ist, and for the moment I created 'freebsd10.h' as a copy of 'freebsd9.h': # cat freebsd10.h #include freebsd9.h #define freebsd8 freebsd8 +Cc: maintainer Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: 10.0-CUR r226986 ports/net-mgmt/net-snmp
On Nov 3, 2011, at 8:25 PM, Matthias Apitz wrote: El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: No, it is not the same. You can either masquerade, by setting UNAME_r and OSVERSION, or by editing the headers and scripts that define them; or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE). Right now the masquerading is probably safer, because there are some problems with the fix that are still being resolved -- and a few ports that may fail despite the fix. But of course if you help to test without masquerading, these problems will be resolved sooner. Well, I will try to help. I have set WITH_FBSD10_FIX in /etc/make.conf; the port ports/net-mgmt/net-snmp installs: /usr/local/include/net-snmp/net-snmp-config.h with: ... /* define the system type include file here */ #define NETSNMP_SYSTEM_INCLUDE_FILE net-snmp/system/freebsd10.h ... but the named header file is not there: # ls -C1 /usr/local/include/net-snmp/system/free* /usr/local/include/net-snmp/system/freebsd.h /usr/local/include/net-snmp/system/freebsd2.h /usr/local/include/net-snmp/system/freebsd3.h /usr/local/include/net-snmp/system/freebsd4.h /usr/local/include/net-snmp/system/freebsd5.h /usr/local/include/net-snmp/system/freebsd6.h /usr/local/include/net-snmp/system/freebsd7.h /usr/local/include/net-snmp/system/freebsd8.h /usr/local/include/net-snmp/system/freebsd9.h I don't know what the correct fix ist, and for the moment I created 'freebsd10.h' as a copy of 'freebsd9.h': # cat freebsd10.h #include freebsd9.h #define freebsd8 freebsd8 +Cc: maintainer You'll need to do more than just that. Take a look at the port history for more details... -Garrett___ 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: 10.0-CUR r226986 ports/security/cyrus-sasl2-saslauthd
El día Thursday, November 03, 2011 a las 01:42:50PM -0400, b. f. escribió: No, it is not the same. You can either masquerade, by setting UNAME_r and OSVERSION, or by editing the headers and scripts that define them; or you can use WITH_FBSD10_FIX for ports that define HAS_CONFIGURE (which is implied by USE_AUTOTOOLS and GNU_CONFIGURE). Right now the masquerading is probably safer, because there are some problems with the fix that are still being resolved -- and a few ports that may fail despite the fix. But of course if you help to test without masquerading, these problems will be resolved sooner. the ports/security/cyrus-sasl2-saslauthd does not install with WITH_FBSD10_FIX; terminates with: cc -O2 -pipe -fno-strict-aliasing -rpath=/usr/lib:/usr/local/lib -o saslauthd mechanisms.o auth_dce.o auth_getpwent.o auth_krb5.o auth_krb4.o auth_pam.o aut h_rimap.o auth_httpform.o auth_shadow.o auth_sia.o auth_sasldb.o lak.o auth_l dap.o cache.o cfile.o krbtf.o utils.o ipc_unix.o ipc_doors.o saslauthd-main.o md5.o -L/usr/lib -lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lcrypto -lasn1 -l roken -lcrypt -lcrypt ../sasldb/.libs/libsasldb.al -lpam cc: ../sasldb/.libs/libsasldb.al: No such file or directory *** Error code 1 installes fine with UNAME_r set to 9-CURRENT; Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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
