Re: HEADS UP: ports/ and 10.0-CURRENT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.09.2011 21:32, Hartmann, O. wrote: > floating like a dead man in the water. I suspect the > conversters/libiconv broke something, since it claims it has > installed libiconv.so.3, but there is never such a shared object > installed! Here's what I did to recover: 1. Deinstall lang/gawk This is necessary so that ports don't try to use it. 2. Reinstall devel/libtool with UNAME_r=9.0-RELEASE Ports using autotools call libtool to know if they should build shared libraries. But libtool disables shared libraries for freebsd1*. You can check what libtool will tell to other ports by doing: libtool --config | grep build_libtool_libs To have shared libraries, this variable must be set to "yes". 3. Reinstall converters/libiconv Now, libiconv.so.3 is back. At this point, my installed ports were running fine. I never reinstalled gettext so it never broke; you may have to. - -- Jean-Sébastien Pédron -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6EIE8ACgkQa+xGJsFYOlNqXQCfVaINbK4Wi+wuyazRLT9aa95o 4dgAoIlecAMgWti/SQhOf4UrVusiNGK0 =G2Bo -END PGP SIGNATURE- ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Sep 28, 2011, at 4:36 PM, Matt wrote: > On 09/28/11 15:41, Hartmann, O. wrote: >> On 09/28/11 22:18, Doug Barton wrote: >>> On 09/28/2011 12:39, Hartmann, O. wrote: The mess started to happen when I tried to "repair" a non CLANG compiling port math/gotoblas with portmaster -vf amth/gotoblas. Since this build binutils and even gettext and libiconv, I guess they got broken. Last I saw was a successful installation report from portmaster. But the libiconv.so.3 wasn't there anymore when I checked! This is a catastrophy ... I'm on FreeBSD 10.0-CURRENT r225844 >>> It's been widely reported on the ports list that you can't do fresh >>> ports compiles on 10-current, and won't be able to until well after >>> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand >>> the 2-digit release version. >>> >>> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or >>> twiddle the version in newvers.sh and rebuild/reinstall your kernel. >>> >>> >>> hth, >>> >>> Doug >>> >> Yes, it has been discussed. But I was too dumb to realise that the >> phenomenon I >> experienced was triggered by this. >> I'll stay tuned and watch when a solution is at hand. >> > I also was apparently too dumb! Making progress with UNAME_r and newvers.sh > as we speak. > I was unable to compile neon29 properly with UNAME_r alone... buildkernel > underway. > At least it's never boring! Please be aware that some user apps like net-smp and kernel modules like nvidia-driver key in on the __FreeBSD_version number. So if it's out of sync with reality, bad things can happen as you're breaking some developers' assumptions. Thanks! -Garrett___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 15:41, Hartmann, O. wrote: On 09/28/11 22:18, Doug Barton wrote: On 09/28/2011 12:39, Hartmann, O. wrote: The mess started to happen when I tried to "repair" a non CLANG compiling port math/gotoblas with portmaster -vf amth/gotoblas. Since this build binutils and even gettext and libiconv, I guess they got broken. Last I saw was a successful installation report from portmaster. But the libiconv.so.3 wasn't there anymore when I checked! This is a catastrophy ... I'm on FreeBSD 10.0-CURRENT r225844 It's been widely reported on the ports list that you can't do fresh ports compiles on 10-current, and won't be able to until well after 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand the 2-digit release version. Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or twiddle the version in newvers.sh and rebuild/reinstall your kernel. hth, Doug Yes, it has been discussed. But I was too dumb to realise that the phenomenon I experienced was triggered by this. I'll stay tuned and watch when a solution is at hand. Regards, Oliver I also was apparently too dumb! Making progress with UNAME_r and newvers.sh as we speak. I was unable to compile neon29 properly with UNAME_r alone... buildkernel underway. At least it's never boring! Thanks all Matt ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 22:18, Doug Barton wrote: > On 09/28/2011 12:39, Hartmann, O. wrote: >> The mess started to happen when I tried to "repair" a non CLANG >> compiling port math/gotoblas with portmaster -vf amth/gotoblas. >> Since this build binutils and even gettext and libiconv, I guess they >> got broken. Last I saw was a successful installation report from >> portmaster. But the libiconv.so.3 wasn't there anymore when I checked! >> >> This is a catastrophy ... >> >> I'm on FreeBSD 10.0-CURRENT r225844 > It's been widely reported on the ports list that you can't do fresh > ports compiles on 10-current, and won't be able to until well after > 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand > the 2-digit release version. > > Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or > twiddle the version in newvers.sh and rebuild/reinstall your kernel. > > > hth, > > Doug > Yes, it has been discussed. But I was too dumb to realise that the phenomenon I experienced was triggered by this. I'll stay tuned and watch when a solution is at hand. Regards, Oliver ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Garrett Cooper writes: >> >> So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 I'm >> not >> going to shoot myself in the foot if I try and update? I would really like to >> avoid downgrading this box.I've altready been bitten once today and had to >> build packages on my tindy and force install. > > Today no, but when someone in changes something in base or ports that > checks for __FreeBSD_version, yes. Since when `uname -r' (kern.osrelease) is dependent on __FreeBSD_version (kern.osreldate)? From what I've seen kensmith@ changed them separately http://svn.freebsd.org/changeset/base/225757 ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Wednesday 28 September 2011 12:53:23 Beech Rintoul wrote: > On Wednesday 28 September 2011 12:47:50 Doug Barton wrote: > > On 09/28/2011 13:45, Beech Rintoul wrote: > > > On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: > > >> On 09/28/2011 12:39, Hartmann, O. wrote: > > >>> The mess started to happen when I tried to "repair" a non CLANG > > >>> compiling port math/gotoblas with portmaster -vf amth/gotoblas. > > >>> Since this build binutils and even gettext and libiconv, I guess they > > >>> got broken. Last I saw was a successful installation report from > > >>> portmaster. But the libiconv.so.3 wasn't there anymore when I > > >>> checked! > > >>> > > >>> This is a catastrophy ... > > >>> > > >>> I'm on FreeBSD 10.0-CURRENT r225844 > > >> > > >> It's been widely reported on the ports list that you can't do fresh > > >> ports compiles on 10-current, and won't be able to until well after > > >> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand > > >> the 2-digit release version. > > >> > > >> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or > > >> twiddle the version in newvers.sh and rebuild/reinstall your kernel. > > >> > > >> > > >> hth, > > >> > > >> Doug > > > > > > So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 > > > I'm not going to shoot myself in the foot if I try and update? I would > > > really like to avoid downgrading this box.I've altready been bitten > > > once today and had to build packages on my tindy and force install. > > > > That should be the case, yes. I haven't tested it yet myself. If you do, > > and it works, let us know and I'll write the UPDATING entry if no one > > else does. > > No problem, I'm building now. Any suggestions as to what port I should try > after the reboot? I'm now at 9.9 and gawk built without problems. So this seems to work at least for the time being. Thanks for the fix, even if it is temporary. :-) If anyone else has a problem port let me know, I'd be happy to run a few. Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html --- ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Wed, Sep 28, 2011 at 1:45 PM, Beech Rintoul wrote: > On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: >> On 09/28/2011 12:39, Hartmann, O. wrote: >> > The mess started to happen when I tried to "repair" a non CLANG >> > compiling port math/gotoblas with portmaster -vf amth/gotoblas. >> > Since this build binutils and even gettext and libiconv, I guess they >> > got broken. Last I saw was a successful installation report from >> > portmaster. But the libiconv.so.3 wasn't there anymore when I checked! >> > >> > This is a catastrophy ... >> > >> > I'm on FreeBSD 10.0-CURRENT r225844 >> >> It's been widely reported on the ports list that you can't do fresh >> ports compiles on 10-current, and won't be able to until well after >> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand >> the 2-digit release version. >> >> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or >> twiddle the version in newvers.sh and rebuild/reinstall your kernel. >> >> >> hth, >> >> Doug > > So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 I'm not > going to shoot myself in the foot if I try and update? I would really like to > avoid downgrading this box.I've altready been bitten once today and had to > build packages on my tindy and force install. Today no, but when someone in changes something in base or ports that checks for __FreeBSD_version, yes. HTH, -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Wednesday 28 September 2011 12:47:50 Doug Barton wrote: > On 09/28/2011 13:45, Beech Rintoul wrote: > > On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: > >> On 09/28/2011 12:39, Hartmann, O. wrote: > >>> The mess started to happen when I tried to "repair" a non CLANG > >>> compiling port math/gotoblas with portmaster -vf amth/gotoblas. > >>> Since this build binutils and even gettext and libiconv, I guess they > >>> got broken. Last I saw was a successful installation report from > >>> portmaster. But the libiconv.so.3 wasn't there anymore when I checked! > >>> > >>> This is a catastrophy ... > >>> > >>> I'm on FreeBSD 10.0-CURRENT r225844 > >> > >> It's been widely reported on the ports list that you can't do fresh > >> ports compiles on 10-current, and won't be able to until well after > >> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand > >> the 2-digit release version. > >> > >> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or > >> twiddle the version in newvers.sh and rebuild/reinstall your kernel. > >> > >> > >> hth, > >> > >> Doug > > > > So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 > > I'm not going to shoot myself in the foot if I try and update? I would > > really like to avoid downgrading this box.I've altready been bitten once > > today and had to build packages on my tindy and force install. > > That should be the case, yes. I haven't tested it yet myself. If you do, > and it works, let us know and I'll write the UPDATING entry if no one > else does. No problem, I'm building now. Any suggestions as to what port I should try after the reboot? Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html --- ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/2011 13:45, Beech Rintoul wrote: > On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: >> On 09/28/2011 12:39, Hartmann, O. wrote: >>> The mess started to happen when I tried to "repair" a non CLANG >>> compiling port math/gotoblas with portmaster -vf amth/gotoblas. >>> Since this build binutils and even gettext and libiconv, I guess they >>> got broken. Last I saw was a successful installation report from >>> portmaster. But the libiconv.so.3 wasn't there anymore when I checked! >>> >>> This is a catastrophy ... >>> >>> I'm on FreeBSD 10.0-CURRENT r225844 >> >> It's been widely reported on the ports list that you can't do fresh >> ports compiles on 10-current, and won't be able to until well after >> 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand >> the 2-digit release version. >> >> Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or >> twiddle the version in newvers.sh and rebuild/reinstall your kernel. >> >> >> hth, >> >> Doug > > So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 I'm > not > going to shoot myself in the foot if I try and update? I would really like to > avoid downgrading this box.I've altready been bitten once today and had to > build packages on my tindy and force install. That should be the case, yes. I haven't tested it yet myself. If you do, and it works, let us know and I'll write the UPDATING entry if no one else does. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Wednesday 28 September 2011 12:18:47 Doug Barton wrote: > On 09/28/2011 12:39, Hartmann, O. wrote: > > The mess started to happen when I tried to "repair" a non CLANG > > compiling port math/gotoblas with portmaster -vf amth/gotoblas. > > Since this build binutils and even gettext and libiconv, I guess they > > got broken. Last I saw was a successful installation report from > > portmaster. But the libiconv.so.3 wasn't there anymore when I checked! > > > > This is a catastrophy ... > > > > I'm on FreeBSD 10.0-CURRENT r225844 > > It's been widely reported on the ports list that you can't do fresh > ports compiles on 10-current, and won't be able to until well after > 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand > the 2-digit release version. > > Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or > twiddle the version in newvers.sh and rebuild/reinstall your kernel. > > > hth, > > Doug So if I change /usr/src/sys/conf/newvers.sh to something like vers 9.9 I'm not going to shoot myself in the foot if I try and update? I would really like to avoid downgrading this box.I've altready been bitten once today and had to build packages on my tindy and force install. Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html --- ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/2011 12:39, Hartmann, O. wrote: > The mess started to happen when I tried to "repair" a non CLANG > compiling port math/gotoblas with portmaster -vf amth/gotoblas. > Since this build binutils and even gettext and libiconv, I guess they > got broken. Last I saw was a successful installation report from > portmaster. But the libiconv.so.3 wasn't there anymore when I checked! > > This is a catastrophy ... > > I'm on FreeBSD 10.0-CURRENT r225844 It's been widely reported on the ports list that you can't do fresh ports compiles on 10-current, and won't be able to until well after 9.0-RELEASE. The primary reason is that auto* stuff doesn't understand the 2-digit release version. Solutions are to set UNAME_r=9.0-CURRENT in your environment, and/or twiddle the version in newvers.sh and rebuild/reinstall your kernel. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 21:30, Matt wrote: > On 09/28/11 12:16, Hartmann, O. wrote: >> On 09/28/11 20:56, Hartmann, O. wrote: >>> On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: > On 09/28/11 20:20, h h wrote: >> "Hartmann, O." writes: >> >>> On 09/28/11 09:26, Hartmann, O. wrote: >>> On 09/28/11 15:47, per...@pluto.rain.com wrote: > Eitan Adler wrote: > >> 2011/9/27 O. Hartmann: >>> Now I understand why some OS vendors have choosen the latin >>> 10 'X' for their tenth version of their operating system ... >> FreeBSD XP anyone? > Are you sure there's a sufficient window of opportunity? :) "Window of Fortune" >>> A stupid question: I experience some strange failures on one of my >>> FreeBSD 10.0-CURRENT/amd64 boxes. >>> libiconv.so.3 is missing for svn. I can not install >>> conversters/libiconv >>> anymore, portbuild compains about a missing >>> libintl.so.9 (huhh?), see below. >> subversion port does not depend on iconv/gettext when WITHOUT_NLS >> is specified. >> >>> Ok, libintl.so.9 is gettext. So I try reinstall gettext and it >>> fails, >>> also! gawk is missing libintl.so.9. So I try to reinstall gawk: >>> portmaster gawk. But gawk complains about no intl found, so it >>> tries to >>> install gettext and gettext complains about not finding >>> libintl.so.9. >> [...] >> >> Try to do WITHOUT_NLS install of lang/gawk. port builds are not >> done in >> clean environment so GNU configure happily prefers gawk over nawk >> in base. >> >> # Check for gawk first since it's generally better. >> AN_MAKEVAR([AWK], [AC_PROG_AWK]) >> AN_PROGRAM([awk], [AC_PROG_AWK]) >> AN_PROGRAM([gawk], [AC_PROG_AWK]) >> AN_PROGRAM([mawk], [AC_PROG_AWK]) >> AN_PROGRAM([nawk], [AC_PROG_AWK]) >> AC_DEFUN([AC_PROG_AWK], >> [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) >> >> Well, you can also deinstall the port. > Even with CLANG, lang/gawk build fine, but it fails installing and > I'm > blind to see what's going on ...: > > Making all in po > Making all in test > root@thor: [gawk] make install > ===> Installing for gawk-4.0.0 > ===>gawk-4.0.0 depends on shared library: sigsegv - found > ===>gawk-4.0.0 depends on shared library: intl - found > ===>Generating temporary packing list > Making install in . > test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" > install -s -o root -g wheel -m 555 gawk pgawk dgawk > '/usr/local/bin' > make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' > 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook > (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk > pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s > gawk awk; fi; exit 0) > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk. > > > Oliver h.h. is right. Deinstall the port and restart the upgrade was the recommended solution for your upgrade blues. -Garrett___ 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" >>> Great ... worked! 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" >> >> Sorry, take verything back. >> >> Deinstalled gawk, reinstalled gawk, worked so far. Did portmaster >> gettext/libiconv. Worked so far, it reported success. But when I then >> try to portsnap/portmaster, I get the same idiocracy again. Now even >> gawk, gettext and libiconv fail to install since there is no >> libintl.so.9: >> >> >> root@thor: [gawk] make install >> ===>gawk-4.0.0 depends on shared library: sigsegv - found >> ===>gawk-4.0.0 depends on shared library: intl - not found >> ===> Verifying install for intl in /usr/ports/devel/gettext >> ===>gettext-0.18.1.1 depends on package: libtool>=2.4 - found >> ===>gettext-0.18.1.1 depends on shared library: iconv.3 - not found >> ===> Verifying install for iconv.3 in /usr/ports/converters/libiconv >> ===> Building for libiconv-1.13.1_1 >> builddir="`pwd`"; cd libcharset&& make all&& make install-lib >> libdir
Re: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 21:16, Hartmann, O. wrote: > On 09/28/11 20:56, Hartmann, O. wrote: >> On 09/28/11 20:41, Garrett Cooper wrote: >>> On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: >>> On 09/28/11 20:20, h h wrote: > "Hartmann, O." writes: > >> On 09/28/11 09:26, Hartmann, O. wrote: >> >>> On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler wrote: > 2011/9/27 O. Hartmann : >> Now I understand why some OS vendors have choosen the latin >> 10 'X' for their tenth version of their operating system ... > FreeBSD XP anyone? Are you sure there's a sufficient window of opportunity? :) >>> "Window of Fortune" >> A stupid question: I experience some strange failures on one of my >> FreeBSD 10.0-CURRENT/amd64 boxes. >> libiconv.so.3 is missing for svn. I can not install conversters/libiconv >> anymore, portbuild compains about a missing >> libintl.so.9 (huhh?), see below. > subversion port does not depend on iconv/gettext when WITHOUT_NLS is > specified. > >> Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, >> also! gawk is missing libintl.so.9. So I try to reinstall gawk: >> portmaster gawk. But gawk complains about no intl found, so it tries to >> install gettext and gettext complains about not finding libintl.so.9. > [...] > > Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in > clean environment so GNU configure happily prefers gawk over nawk in base. > > # Check for gawk first since it's generally better. > AN_MAKEVAR([AWK], [AC_PROG_AWK]) > AN_PROGRAM([awk], [AC_PROG_AWK]) > AN_PROGRAM([gawk], [AC_PROG_AWK]) > AN_PROGRAM([mawk], [AC_PROG_AWK]) > AN_PROGRAM([nawk], [AC_PROG_AWK]) > AC_DEFUN([AC_PROG_AWK], > [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) > > Well, you can also deinstall the port. Even with CLANG, lang/gawk build fine, but it fails installing and I'm blind to see what's going on ...: Making all in po Making all in test root@thor: [gawk] make install ===> Installing for gawk-4.0.0 ===> gawk-4.0.0 depends on shared library: sigsegv - found ===> gawk-4.0.0 depends on shared library: intl - found ===> Generating temporary packing list Making install in . test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s gawk awk; fi; exit 0) *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk. Oliver >>> h.h. is right. Deinstall the port and restart the upgrade was the >>> recommended solution for your upgrade blues. >>> -Garrett___ >>> 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" >> Great ... worked! 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" > > Sorry, take verything back. > > Deinstalled gawk, reinstalled gawk, worked so far. Did portmaster > gettext/libiconv. Worked so far, it reported success. But when I then > try to portsnap/portmaster, I get the same idiocracy again. Now even > gawk, gettext and libiconv fail to install since there is no libintl.so.9: > > > root@thor: [gawk] make install > ===> gawk-4.0.0 depends on shared library: sigsegv - found > ===> gawk-4.0.0 depends on shared library: intl - not found > ===>Verifying install for intl in /usr/ports/devel/gettext > ===> gettext-0.18.1.1 depends on package: libtool>=2.4 - found > ===> gettext-0.18.1.1 depends on shared library: iconv.3 - not found > ===>Verifying install for iconv.3 in /usr/ports/converters/libiconv > ===> Building for libiconv-1.13.1_1 > builddir="`pwd`"; cd libcharset && make all && make install-lib > libdir="$builddir/lib" includedir="$builddir/lib" > cd lib && make all > /bin/sh /usr/local/bin/libtool --mode=link --tag=CC clang -O3 > -fno-strict-aliasing -pipe -march=native -std=gnu89 -o libcharset.la > -rpath /usr/local/lib -versi
Re: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 12:16, Hartmann, O. wrote: On 09/28/11 20:56, Hartmann, O. wrote: On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: On 09/28/11 20:20, h h wrote: "Hartmann, O." writes: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler wrote: 2011/9/27 O. Hartmann: Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating system ... FreeBSD XP anyone? Are you sure there's a sufficient window of opportunity? :) "Window of Fortune" A stupid question: I experience some strange failures on one of my FreeBSD 10.0-CURRENT/amd64 boxes. libiconv.so.3 is missing for svn. I can not install conversters/libiconv anymore, portbuild compains about a missing libintl.so.9 (huhh?), see below. subversion port does not depend on iconv/gettext when WITHOUT_NLS is specified. Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, also! gawk is missing libintl.so.9. So I try to reinstall gawk: portmaster gawk. But gawk complains about no intl found, so it tries to install gettext and gettext complains about not finding libintl.so.9. [...] Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in clean environment so GNU configure happily prefers gawk over nawk in base. # Check for gawk first since it's generally better. AN_MAKEVAR([AWK], [AC_PROG_AWK]) AN_PROGRAM([awk], [AC_PROG_AWK]) AN_PROGRAM([gawk], [AC_PROG_AWK]) AN_PROGRAM([mawk], [AC_PROG_AWK]) AN_PROGRAM([nawk], [AC_PROG_AWK]) AC_DEFUN([AC_PROG_AWK], [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) Well, you can also deinstall the port. Even with CLANG, lang/gawk build fine, but it fails installing and I'm blind to see what's going on ...: Making all in po Making all in test root@thor: [gawk] make install ===> Installing for gawk-4.0.0 ===>gawk-4.0.0 depends on shared library: sigsegv - found ===>gawk-4.0.0 depends on shared library: intl - found ===>Generating temporary packing list Making install in . test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s gawk awk; fi; exit 0) *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk. Oliver h.h. is right. Deinstall the port and restart the upgrade was the recommended solution for your upgrade blues. -Garrett___ 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" Great ... worked! 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" Sorry, take verything back. Deinstalled gawk, reinstalled gawk, worked so far. Did portmaster gettext/libiconv. Worked so far, it reported success. But when I then try to portsnap/portmaster, I get the same idiocracy again. Now even gawk, gettext and libiconv fail to install since there is no libintl.so.9: root@thor: [gawk] make install ===>gawk-4.0.0 depends on shared library: sigsegv - found ===>gawk-4.0.0 depends on shared library: intl - not found ===> Verifying install for intl in /usr/ports/devel/gettext ===>gettext-0.18.1.1 depends on package: libtool>=2.4 - found ===>gettext-0.18.1.1 depends on shared library: iconv.3 - not found ===> Verifying install for iconv.3 in /usr/ports/converters/libiconv ===> Building for libiconv-1.13.1_1 builddir="`pwd`"; cd libcharset&& make all&& make install-lib libdir="$builddir/lib" includedir="$builddir/lib" cd lib&& make all /bin/sh /usr/local/bin/libtool --mode=link --tag=CC clang -O3 -fno-strict-aliasing -pipe -march=native -std=gnu89 -o libcharset.la -rpath /usr/local/lib -version-info 1 -no-undefined localcharset.lo relocatable.lo libtool: link: ar cru .libs/libcharset.a localcharset.o relocatable.o Shared object "libintl.so.9" not found, required by "ar"*** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.13.1/libcharset/lib. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.13.1/libcharset. *** Error code 1 Stop in /usr/ports/converters/libiconv/work/libiconv-1.13.1. *** Error code 1 Stop in /usr/ports/converters/libiconv. **
Re: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 20:56, Hartmann, O. wrote: > On 09/28/11 20:41, Garrett Cooper wrote: >> On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: >> >>> On 09/28/11 20:20, h h wrote: "Hartmann, O." writes: > On 09/28/11 09:26, Hartmann, O. wrote: > >> On 09/28/11 15:47, per...@pluto.rain.com wrote: >>> Eitan Adler wrote: >>> 2011/9/27 O. Hartmann : > Now I understand why some OS vendors have choosen the latin > 10 'X' for their tenth version of their operating system ... FreeBSD XP anyone? >>> Are you sure there's a sufficient window of opportunity? :) >> "Window of Fortune" > A stupid question: I experience some strange failures on one of my > FreeBSD 10.0-CURRENT/amd64 boxes. > libiconv.so.3 is missing for svn. I can not install conversters/libiconv > anymore, portbuild compains about a missing > libintl.so.9 (huhh?), see below. subversion port does not depend on iconv/gettext when WITHOUT_NLS is specified. > Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, > also! gawk is missing libintl.so.9. So I try to reinstall gawk: > portmaster gawk. But gawk complains about no intl found, so it tries to > install gettext and gettext complains about not finding libintl.so.9. [...] Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in clean environment so GNU configure happily prefers gawk over nawk in base. # Check for gawk first since it's generally better. AN_MAKEVAR([AWK], [AC_PROG_AWK]) AN_PROGRAM([awk], [AC_PROG_AWK]) AN_PROGRAM([gawk], [AC_PROG_AWK]) AN_PROGRAM([mawk], [AC_PROG_AWK]) AN_PROGRAM([nawk], [AC_PROG_AWK]) AC_DEFUN([AC_PROG_AWK], [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) Well, you can also deinstall the port. >>> Even with CLANG, lang/gawk build fine, but it fails installing and I'm >>> blind to see what's going on ...: >>> >>> Making all in po >>> Making all in test >>> root@thor: [gawk] make install >>> ===> Installing for gawk-4.0.0 >>> ===> gawk-4.0.0 depends on shared library: sigsegv - found >>> ===> gawk-4.0.0 depends on shared library: intl - found >>> ===> Generating temporary packing list >>> Making install in . >>> test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" >>> install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' >>> make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' >>> 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook >>> (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk >>> pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s >>> gawk awk; fi; exit 0) >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/gawk. >>> >>> >>> Oliver >> h.h. is right. Deinstall the port and restart the upgrade was the >> recommended solution for your upgrade blues. >> -Garrett___ >> 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" > Great ... worked! 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" Sorry, take verything back. Deinstalled gawk, reinstalled gawk, worked so far. Did portmaster gettext/libiconv. Worked so far, it reported success. But when I then try to portsnap/portmaster, I get the same idiocracy again. Now even gawk, gettext and libiconv fail to install since there is no libintl.so.9: root@thor: [gawk] make install ===> gawk-4.0.0 depends on shared library: sigsegv - found ===> gawk-4.0.0 depends on shared library: intl - not found ===>Verifying install for intl in /usr/ports/devel/gettext ===> gettext-0.18.1.1 depends on package: libtool>=2.4 - found ===> gettext-0.18.1.1 depends on shared library: iconv.3 - not found ===>Verifying install for iconv.3 in /usr/ports/converters/libiconv ===> Building for libiconv-1.13.1_1 builddir="`pwd`"; cd libcharset && make all && make install-lib libdir="$builddir/lib" includedir="$builddir/lib" cd lib && make all /bin/sh /usr/local/bin/libtool --mode=link --tag=CC clang -O3 -fno-strict-aliasing -pipe -march=native -std=gnu89 -o libcharset.la -rpath /usr/local/lib -version-info 1 -no-undefined localcharset.lo relocatable.lo libtool: link: ar cru .libs/libcharset.a localcharset.o relocatable.o Shared object "libintl.so.9" not found, require
Re: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 20:41, Garrett Cooper wrote: > On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: > >> On 09/28/11 20:20, h h wrote: >>> "Hartmann, O." writes: >>> On 09/28/11 09:26, Hartmann, O. wrote: > On 09/28/11 15:47, per...@pluto.rain.com wrote: >> Eitan Adler wrote: >> >>> 2011/9/27 O. Hartmann : Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating system ... >>> FreeBSD XP anyone? >> Are you sure there's a sufficient window of opportunity? :) > "Window of Fortune" A stupid question: I experience some strange failures on one of my FreeBSD 10.0-CURRENT/amd64 boxes. libiconv.so.3 is missing for svn. I can not install conversters/libiconv anymore, portbuild compains about a missing libintl.so.9 (huhh?), see below. >>> subversion port does not depend on iconv/gettext when WITHOUT_NLS is >>> specified. >>> Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, also! gawk is missing libintl.so.9. So I try to reinstall gawk: portmaster gawk. But gawk complains about no intl found, so it tries to install gettext and gettext complains about not finding libintl.so.9. >>> [...] >>> >>> Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in >>> clean environment so GNU configure happily prefers gawk over nawk in base. >>> >>> # Check for gawk first since it's generally better. >>> AN_MAKEVAR([AWK], [AC_PROG_AWK]) >>> AN_PROGRAM([awk], [AC_PROG_AWK]) >>> AN_PROGRAM([gawk], [AC_PROG_AWK]) >>> AN_PROGRAM([mawk], [AC_PROG_AWK]) >>> AN_PROGRAM([nawk], [AC_PROG_AWK]) >>> AC_DEFUN([AC_PROG_AWK], >>> [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) >>> >>> Well, you can also deinstall the port. >> Even with CLANG, lang/gawk build fine, but it fails installing and I'm >> blind to see what's going on ...: >> >> Making all in po >> Making all in test >> root@thor: [gawk] make install >> ===> Installing for gawk-4.0.0 >> ===> gawk-4.0.0 depends on shared library: sigsegv - found >> ===> gawk-4.0.0 depends on shared library: intl - found >> ===> Generating temporary packing list >> Making install in . >> test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" >> install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' >> make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' >> 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook >> (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk >> pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s >> gawk awk; fi; exit 0) >> *** Error code 1 >> >> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >> *** Error code 1 >> >> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >> *** Error code 1 >> >> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >> *** Error code 1 >> >> Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. >> *** Error code 1 >> >> Stop in /usr/ports/lang/gawk. >> >> >> Oliver > h.h. is right. Deinstall the port and restart the upgrade was the recommended > solution for your upgrade blues. > -Garrett___ > 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" Great ... worked! 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"
Re: HEADS UP: ports/ and 10.0-CURRENT
On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: > On 09/28/11 20:20, h h wrote: >> "Hartmann, O." writes: >> >>> On 09/28/11 09:26, Hartmann, O. wrote: >>> On 09/28/11 15:47, per...@pluto.rain.com wrote: > Eitan Adler wrote: > >> 2011/9/27 O. Hartmann : >>> Now I understand why some OS vendors have choosen the latin >>> 10 'X' for their tenth version of their operating system ... >> FreeBSD XP anyone? > Are you sure there's a sufficient window of opportunity? :) "Window of Fortune" >>> A stupid question: I experience some strange failures on one of my >>> FreeBSD 10.0-CURRENT/amd64 boxes. >>> libiconv.so.3 is missing for svn. I can not install conversters/libiconv >>> anymore, portbuild compains about a missing >>> libintl.so.9 (huhh?), see below. >> subversion port does not depend on iconv/gettext when WITHOUT_NLS is >> specified. >> >>> Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, >>> also! gawk is missing libintl.so.9. So I try to reinstall gawk: >>> portmaster gawk. But gawk complains about no intl found, so it tries to >>> install gettext and gettext complains about not finding libintl.so.9. >> [...] >> >> Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in >> clean environment so GNU configure happily prefers gawk over nawk in base. >> >> # Check for gawk first since it's generally better. >> AN_MAKEVAR([AWK], [AC_PROG_AWK]) >> AN_PROGRAM([awk], [AC_PROG_AWK]) >> AN_PROGRAM([gawk], [AC_PROG_AWK]) >> AN_PROGRAM([mawk], [AC_PROG_AWK]) >> AN_PROGRAM([nawk], [AC_PROG_AWK]) >> AC_DEFUN([AC_PROG_AWK], >> [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) >> >> Well, you can also deinstall the port. > > Even with CLANG, lang/gawk build fine, but it fails installing and I'm > blind to see what's going on ...: > > Making all in po > Making all in test > root@thor: [gawk] make install > ===> Installing for gawk-4.0.0 > ===> gawk-4.0.0 depends on shared library: sigsegv - found > ===> gawk-4.0.0 depends on shared library: intl - found > ===> Generating temporary packing list > Making install in . > test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" > install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' > make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' > 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook > (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk > pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s > gawk awk; fi; exit 0) > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. > *** Error code 1 > > Stop in /usr/ports/lang/gawk. > > > Oliver h.h. is right. Deinstall the port and restart the upgrade was the recommended solution for your upgrade blues. -Garrett___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 20:20, h h wrote: > "Hartmann, O." writes: > >> On 09/28/11 09:26, Hartmann, O. wrote: >> >>> On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler wrote: > 2011/9/27 O. Hartmann : >> Now I understand why some OS vendors have choosen the latin >> 10 'X' for their tenth version of their operating system ... > FreeBSD XP anyone? Are you sure there's a sufficient window of opportunity? :) >>> "Window of Fortune" >> A stupid question: I experience some strange failures on one of my >> FreeBSD 10.0-CURRENT/amd64 boxes. >> libiconv.so.3 is missing for svn. I can not install conversters/libiconv >> anymore, portbuild compains about a missing >> libintl.so.9 (huhh?), see below. > subversion port does not depend on iconv/gettext when WITHOUT_NLS is > specified. > >> Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, >> also! gawk is missing libintl.so.9. So I try to reinstall gawk: >> portmaster gawk. But gawk complains about no intl found, so it tries to >> install gettext and gettext complains about not finding libintl.so.9. > [...] > > Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in > clean environment so GNU configure happily prefers gawk over nawk in base. > > # Check for gawk first since it's generally better. > AN_MAKEVAR([AWK], [AC_PROG_AWK]) > AN_PROGRAM([awk], [AC_PROG_AWK]) > AN_PROGRAM([gawk], [AC_PROG_AWK]) > AN_PROGRAM([mawk], [AC_PROG_AWK]) > AN_PROGRAM([nawk], [AC_PROG_AWK]) > AC_DEFUN([AC_PROG_AWK], > [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) > > Well, you can also deinstall the port. > ___ > 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" Even with CLANG, lang/gawk build fine, but it fails installing and I'm blind to see what's going on ...: Making all in po Making all in test root@thor: [gawk] make install ===> Installing for gawk-4.0.0 ===> gawk-4.0.0 depends on shared library: sigsegv - found ===> gawk-4.0.0 depends on shared library: intl - found ===> Generating temporary packing list Making install in . test -z "/usr/local/bin" || /usr/local/bin/gmkdir -p "/usr/local/bin" install -s -o root -g wheel -m 555 gawk pgawk dgawk '/usr/local/bin' make 'CFLAGS=-O3 -fno-strict-aliasing -pipe -march=native' 'LDFLAGS=-export-dynamic -L/usr/local/lib' install-exec-hook (cd /usr/local/bin; ln gawk gawk-4.0.0 2>/dev/null ; ln pgawk pgawk-4.0.0 2>/dev/null ; if ! /usr/bin/which -s awk; thenln -s gawk awk; fi; exit 0) *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk/work/gawk-4.0.0. *** Error code 1 Stop in /usr/ports/lang/gawk. Oliver ___ 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: HEADS UP: ports/ and 10.0-CURRENT
"Hartmann, O." writes: > On 09/28/11 09:26, Hartmann, O. wrote: > >> On 09/28/11 15:47, per...@pluto.rain.com wrote: >>> Eitan Adler wrote: >>> 2011/9/27 O. Hartmann : > Now I understand why some OS vendors have choosen the latin > 10 'X' for their tenth version of their operating system ... FreeBSD XP anyone? >>> Are you sure there's a sufficient window of opportunity? :) >> "Window of Fortune" > > A stupid question: I experience some strange failures on one of my > FreeBSD 10.0-CURRENT/amd64 boxes. > libiconv.so.3 is missing for svn. I can not install conversters/libiconv > anymore, portbuild compains about a missing > libintl.so.9 (huhh?), see below. subversion port does not depend on iconv/gettext when WITHOUT_NLS is specified. > > Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, > also! gawk is missing libintl.so.9. So I try to reinstall gawk: > portmaster gawk. But gawk complains about no intl found, so it tries to > install gettext and gettext complains about not finding libintl.so.9. [...] Try to do WITHOUT_NLS install of lang/gawk. port builds are not done in clean environment so GNU configure happily prefers gawk over nawk in base. # Check for gawk first since it's generally better. AN_MAKEVAR([AWK], [AC_PROG_AWK]) AN_PROGRAM([awk], [AC_PROG_AWK]) AN_PROGRAM([gawk], [AC_PROG_AWK]) AN_PROGRAM([mawk], [AC_PROG_AWK]) AN_PROGRAM([nawk], [AC_PROG_AWK]) AC_DEFUN([AC_PROG_AWK], [AC_CHECK_PROGS(AWK, gawk mawk nawk awk, )]) Well, you can also deinstall the port. ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Sep 28, 2011, at 10:29 AM, Hartmann, O. wrote: > On 09/28/11 09:26, Hartmann, O. wrote: >> On 09/28/11 15:47, per...@pluto.rain.com wrote: >>> Eitan Adler wrote: >>> 2011/9/27 O. Hartmann : > Now I understand why some OS vendors have choosen the latin > 10 'X' for their tenth version of their operating system ... FreeBSD XP anyone? >>> Are you sure there's a sufficient window of opportunity? :) >> "Window of Fortune" > > A stupid question: I experience some strange failures on one of my > FreeBSD 10.0-CURRENT/amd64 boxes. > libiconv.so.3 is missing for svn. I can not install conversters/libiconv > anymore, portbuild compains about a missing > libintl.so.9 (huhh?), see below. > > Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, > also! gawk is missing libintl.so.9. So I try to reinstall gawk: > portmaster gawk. But gawk complains about no intl found, so it tries to > install gettext and gettext complains about not finding libintl.so.9. > > > I'm confused! Is this due to the FreeBSD 10 issue? If not, how to repair? > > > > checking for ptrdiff_t integer literal suffix... l > checking for size_t integer literal suffix... Shared object > "libintl.so.9" not found, required by "pg_config"ul > checking for sig_atomic_t integer literal suffix... l > checking for wchar_t integer literal suffix... > checking for wint_t integer literal suffix... > checking for random.h... no > checking for struct random_data... no > checking whether is standalone... (cached) yes > configure: creating ./config.status > config.status: creating Makefile > Shared object "libintl.so.9" not found, required by "gawk"config.status: > error: could not create Makefile > ===> Script "configure" failed unexpectedly. > Please report the problem to gn...@freebsd.org [maintainer] and attach the > "/usr/ports/converters/libiconv/work/libiconv-1.13.1/config.log" including > the output of the failure of your make command. Also, it might be a good > idea > to provide an overview of all packages installed on your system (e.g. an `ls > /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/converters/libiconv. > *** Error code 1 > > Stop in /usr/ports/converters/libiconv. > > ===>>> make failed for converters/libiconv > ===>>> Aborting update > > Terminated > > ===>>> You can restart from the point of failure with this command line: > portmaster converters/libiconv Oh great.. the gawk/libintl chicken and egg problem again because the port was updated (it's in the current or ports archives, 1.5 years ago -- search for gawk). IIRC all you need to do is manually update gawk, then libintl, etc. Thanks, -Garrett___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 09:26, Hartmann, O. wrote: > On 09/28/11 15:47, per...@pluto.rain.com wrote: >> Eitan Adler wrote: >> >>> 2011/9/27 O. Hartmann : Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating system ... >>> FreeBSD XP anyone? >> Are you sure there's a sufficient window of opportunity? :) > "Window of Fortune" > ___ > 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" A stupid question: I experience some strange failures on one of my FreeBSD 10.0-CURRENT/amd64 boxes. libiconv.so.3 is missing for svn. I can not install conversters/libiconv anymore, portbuild compains about a missing libintl.so.9 (huhh?), see below. Ok, libintl.so.9 is gettext. So I try reinstall gettext and it fails, also! gawk is missing libintl.so.9. So I try to reinstall gawk: portmaster gawk. But gawk complains about no intl found, so it tries to install gettext and gettext complains about not finding libintl.so.9. I'm confused! Is this due to the FreeBSD 10 issue? If not, how to repair? checking for ptrdiff_t integer literal suffix... l checking for size_t integer literal suffix... Shared object "libintl.so.9" not found, required by "pg_config"ul checking for sig_atomic_t integer literal suffix... l checking for wchar_t integer literal suffix... checking for wint_t integer literal suffix... checking for random.h... no checking for struct random_data... no checking whether is standalone... (cached) yes configure: creating ./config.status config.status: creating Makefile Shared object "libintl.so.9" not found, required by "gawk"config.status: error: could not create Makefile ===> Script "configure" failed unexpectedly. Please report the problem to gn...@freebsd.org [maintainer] and attach the "/usr/ports/converters/libiconv/work/libiconv-1.13.1/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/converters/libiconv. *** Error code 1 Stop in /usr/ports/converters/libiconv. ===>>> make failed for converters/libiconv ===>>> Aborting update Terminated ===>>> You can restart from the point of failure with this command line: portmaster converters/libiconv ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Eitan Adler wrote: > 2011/9/27 O. Hartmann : > > Now I understand why some OS vendors have choosen the latin > > 10 'X' for their tenth version of their operating system ... > > FreeBSD XP anyone? Are you sure there's a sufficient window of opportunity? :) ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/28/11 15:47, per...@pluto.rain.com wrote: > Eitan Adler wrote: > >> 2011/9/27 O. Hartmann : >>> Now I understand why some OS vendors have choosen the latin >>> 10 'X' for their tenth version of their operating system ... >> FreeBSD XP anyone? > Are you sure there's a sufficient window of opportunity? :) "Window of Fortune" ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Michael Butler writes: > On 09/27/11 02:37, Daniel O'Connor wrote: > >> >> On 27/09/2011, at 13:33, Ade Lovett wrote: >>> That is to say, until 9.0-R happens, and for some considerable period >>> afterwards, ya'll can pretty much expect ports/ to be non-functional on >>> HEAD. PRs mentioning this will be gleefully closed referencing this >>> message. >> >> I imagine you can work around it by setting UNAME_r=9.0-CURRENT before >> building stuff. > > In some instances, this is insufficient. For multimedia/vlc, adding > "--host=i386-portbld-freebsd9" to "CONFIGURE_ARGS" in the Makefile is > required, multimedia/vlc builds just fine here on 10.0-CURRENT with UNAME_r. I guess you're using sudo(8) which *by default* doesn't preserve environment unlike su(1). Try using `env_keep', `!env_reset' or `-E' # stay away from /stable/9 as far as possible $ export UNAME_r='9.9-BLAH' $ sudo sh -c 'echo $UNAME_r' $ sudo -E sh -c 'echo $UNAME_r' 9.9-BLAH $ su root -c 'echo $UNAME_r' 9.9-BLAH ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/27/11 02:37, Daniel O'Connor wrote: On 27/09/2011, at 13:33, Ade Lovett wrote: That is to say, until 9.0-R happens, and for some considerable period afterwards, ya'll can pretty much expect ports/ to be non-functional on HEAD. PRs mentioning this will be gleefully closed referencing this message. I imagine you can work around it by setting UNAME_r=9.0-CURRENT before building stuff. In some instances, this is insufficient. For multimedia/vlc, adding "--host=i386-portbld-freebsd9" to "CONFIGURE_ARGS" in the Makefile is required, imb ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Hi-- On Sep 27, 2011, at 11:50 AM, Gleb Kurtsou wrote: > It's more exciting than that. FreeBSD >= 10 is already seized by Apple :) > > http://www.google.com/codesearch#search/&q=__FreeBSD__%5CW%2B10&type=cs MacOS X doesn't define __FreeBSD__ either in CPP macros or the system headers: % touch foo.h; cpp -dM foo.h | grep __FreeBSD__ % cpp --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) 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. Regards, -- -Chuck ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Sep 27, 2011, at 8:50 PM, Gleb Kurtsou wrote: > On (26/09/2011 23:03), 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". > > It's more exciting than that. FreeBSD >= 10 is already seized by > Apple :) > > http://www.google.com/codesearch#search/&q=__FreeBSD__%5CW%2B10&type=cs > That seems to be a FUSE-ism. __FreeBSD__ isn't defined anywhere on my OSX system.___ 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: HEADS UP: ports/ and 10.0-CURRENT
On (26/09/2011 23:03), 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". It's more exciting than that. FreeBSD >= 10 is already seized by Apple :) http://www.google.com/codesearch#search/&q=__FreeBSD__%5CW%2B10&type=cs > > This is going to be some fairly fundamental breakage. > > However, until such time as 9.0-RELEASE is completely out of the door, > with autotools hat on, I will _not_ be committing any changes to > infrastructural ports to "fix" this. > > That is to say, until 9.0-R happens, and for some considerable period > afterwards, ya'll can pretty much expect ports/ to be non-functional on > HEAD. PRs mentioning this will be gleefully closed referencing this > message. > > -aDe > > Reply-To set to me. Please honor it. > > > ___ > 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" ___ 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: 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-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: HEADS UP: ports/ and 10.0-CURRENT
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 ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 09/27/11 16:27, Matthew D. Fuller wrote: > On Tue, Sep 27, 2011 at 09:36:17AM -0400 I heard the voice of > Robert Huff, and lo! it spake thus: >> Adrian Chadd writes: >>> Our children will be dealing with Y2038. :-) >> Statistically, some of us will. > Actually, I had to deal with it just last week... > > I was there, tomorrow. ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Tue, Sep 27, 2011 at 09:36:17AM -0400 I heard the voice of Robert Huff, and lo! it spake thus: > Adrian Chadd writes: > > Our children will be dealing with Y2038. :-) > > Statistically, some of us will. Actually, I had to deal with it just last week... -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Adrian Chadd writes: > >> we can leave that to our grand children to figure out though 8) > > > > Wasn't that what people said about two-digit years? > > Our children will be dealing with Y2038. :-) Statistically, some of us will. Robert Huff ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 27 September 2011 13:57, Adrian Chadd wrote: > On 27 September 2011 20:22, Robert Huff wrote: > > > > krad writes: > >> we can leave that to our grand children to figure out though 8) > > > >Wasn't that what people said about two-digit years? > > Our children will be dealing with Y2038. :-) > > I'm sure some of us old-timers will be looking for high-paid 2038 consultancy work to fund our lavish retirement plans... ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Tue, Sep 27, 2011 at 08:22:54AM -0400, Robert Huff wrote: > > krad writes: > > we can leave that to our grand children to figure out though 8) > > Wasn't that what people said about two-digit years? Not quite. There they mostly said "No way that this program will still be in use when two-digit years becomes a problem!" -- Erik Trulsson ertr1...@student.uu.se ___ 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: HEADS UP: ports/ and 10.0-CURRENT
2011/9/27 O. Hartmann : > Now I understand why some OS vendors have choosen the latin 10 'X' for their > tenth version of their operating system ... FreeBSD XP anyone? > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Eitan Adler ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 27 September 2011 20:22, Robert Huff wrote: > > krad writes: >> we can leave that to our grand children to figure out though 8) > > Wasn't that what people said about two-digit years? Our children will be dealing with Y2038. :-) Adrian ___ 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: HEADS UP: ports/ and 10.0-CURRENT
krad writes: > we can leave that to our grand children to figure out though 8) Wasn't that what people said about two-digit years? Robert Huff ___ 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: HEADS UP: ports/ and 10.0-CURRENT
Eduardo Morras writes:
> At 11:18 27/09/2011, Anton Shterenlikht wrote:
>
>> > 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.
>
>
> Or move to hexadecimal
>
> $ export UNAME_r='A.0-CURRENT'
Wouldn't this fail if version is parsed with regex?
# from mysql
ELSEIF(CMAKE_SYSTEM_NAME MATCHES "FreeBSD")
STRING(REGEX MATCH "[0-9]+\\.[0-9]+" VER "${CMAKE_SYSTEM_VERSION}")
SET(DEFAULT_PLATFORM "${CMAKE_SYSTEM_NAME}${VER}")
___
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: HEADS UP: ports/ and 10.0-CURRENT
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. > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > ___ > 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" > we can leave that to our grand children to figure out though 8) ___ 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: outside the box (Re: HEADS UP: ports/ and 10.0-CURRENT)
On 09/27/11 16:46, per...@pluto.rain.com wrote: Ade Lovett wrote: The undeniable fact is that configure scripts in general have chosen to do things a certain way. Unfortunately for us (us being FreeBSD), we have now broken these conceptions by moving to a dual-digit major release. I don't suppose REVISION="A.1" i.e. using a single hex digit instead of two decimal digits, would work any better :) ... it will only postpone the agony ... better to deal now than shifting it to the future ... ___ 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"
outside the box (Re: HEADS UP: ports/ and 10.0-CURRENT)
Ade Lovett wrote: > The undeniable fact is that configure scripts in general have > chosen to do things a certain way. Unfortunately for us (us > being FreeBSD), we have now broken these conceptions by moving > to a dual-digit major release. I don't suppose REVISION="A.1" i.e. using a single hex digit instead of two decimal digits, would work any better :) (IIRC alphas do sort after numerics, at least in the C locale.) ___ 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: HEADS UP: ports/ and 10.0-CURRENT
At 11:18 27/09/2011, Anton Shterenlikht wrote: > 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. Or move to hexadecimal $ export UNAME_r='A.0-CURRENT' ___ 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: HEADS UP: ports/ and 10.0-CURRENT
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. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: HEADS UP: ports/ and 10.0-CURRENT
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 ... ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Tue, 27 Sep 2011, 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' Assuming that a script's detection algorithm is simple. Please see http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2007-07/msg00597.html for a more complete masquerading algorithm.p -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
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' ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On 27/09/2011, at 13:33, Ade Lovett wrote: > That is to say, until 9.0-R happens, and for some considerable period > afterwards, ya'll can pretty much expect ports/ to be non-functional on > HEAD. PRs mentioning this will be gleefully closed referencing this > message. I imagine you can work around it by setting UNAME_r=9.0-CURRENT before building stuff. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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: HEADS UP: ports/ and 10.0-CURRENT
> It just means that folks didn't plan ahead and didn't think up > proper contingency plans. First off, apologies to Garrett, I'm not picking on you directly, but I kinda knew this would come up. The undeniable fact is that configure scripts in general have chosen to do things a certain way. Unfortunately for us (us being FreeBSD), we have now broken these conceptions by moving to a dual-digit major release. Emails have been passed around (somewhere starting around the 7.x series when it became obvious we would be hitting 10.x a lot sooner than expected). It is no-one's fault that 23,000+ third party applications couldn't be tweaked prior to a trivial change in /sys/conf/newvers.sh that resulted in this "oops". The message I wanted to set across is that until such time as us ports folks have had a chance to really work out the damage, and start on fixing it, then for those running 10-CURRENT, things are likely to be non-linear for a while. Our primary responsibility right now is to ensure that a proper set of packages gets built for the impending 9.0-RELEASE. We haven't forgotten you bleeding edge folks, it's just that right now, you're somewhat down the food chain. Make no mistake. This move to a double-digit major version number is going to cause serious pain. We will do our best to fix, hack, slash, and whatever around it, but right now the focus is the last of our remaining single-digit releases. Until that is out the door, do not be expecting tree-wide commits to fix things. -aDe ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 10:15 PM, Kevin Oberman wrote: > On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote: >> It's not the FreeBSD dev's fault. Unfortunately the autotools folks >> were microoptimizing and didn't consider that the future would come >> sooner than it actually did. > > First, I'm not complaining or criticizing any of the developers and I > am very grateful to > aDe for maintaining them as I get a headache every time I start looking at > them. > > I am baffled in my attempts to parse "didn't consider that the future > would come sooner > than it actually did". Is that what you really meant, because it's > self-contradictory? Or > am I just confused. It just means that folks didn't plan ahead and didn't think up proper contingency plans. FWIW FreeBSD has developed faster in the last couple of years than most folks would have expected -- including myself -- and the release cycles reflect that change. That's more of what I was addressing in my previous reply. Corner cases are the bane of all software developers. -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote: > It's not the FreeBSD dev's fault. Unfortunately the autotools folks > were microoptimizing and didn't consider that the future would come > sooner than it actually did. Garrett, First, I'm not complaining or criticizing any of the developers and I am very grateful to aDe for maintaining them as I get a headache every time I start looking at them. I am baffled in my attempts to parse "didn't consider that the future would come sooner than it actually did". Is that what you really meant, because it's self-contradictory? Or am I just confused. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ 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: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 9:56 PM, Kevin Oberman wrote: > 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". >> >> This is going to be some fairly fundamental breakage. >> >> However, until such time as 9.0-RELEASE is completely out of the door, >> with autotools hat on, I will _not_ be committing any changes to >> infrastructural ports to "fix" this. >> >> That is to say, until 9.0-R happens, and for some considerable period >> afterwards, ya'll can pretty much expect ports/ to be non-functional on >> HEAD. PRs mentioning this will be gleefully closed referencing this >> message. > > aDe, > > Could an entry to this effect be added to UPDATING (with a matching > entry when ports/ is "unbroken"). Being a pessimist, ports will never be fully unbroken unless all the thousands of autotools based ports as fixed, due to unfortunately code duplication. That being said, I think that a note in /usr/ports/UPDATING as well as /usr/src/UPDATING is a VERY good idea. > Anyone running CURRENT should be reading your message, but I'm a "belt > and suspenders" type of > guy on this sort of thing. Backing out of CURRENT and moving to > 9-STABLE can be a REAL pain that > will likely rapidly get worse as HEAD gets less and less frozen. It's not the FreeBSD dev's fault. Unfortunately the autotools folks were microoptimizing and didn't consider that the future would come sooner than it actually did. Thanks, -Garrett ___ 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: HEADS UP: ports/ and 10.0-CURRENT
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". > > This is going to be some fairly fundamental breakage. > > However, until such time as 9.0-RELEASE is completely out of the door, > with autotools hat on, I will _not_ be committing any changes to > infrastructural ports to "fix" this. > > That is to say, until 9.0-R happens, and for some considerable period > afterwards, ya'll can pretty much expect ports/ to be non-functional on > HEAD. PRs mentioning this will be gleefully closed referencing this > message. aDe, Could an entry to this effect be added to UPDATING (with a matching entry when ports/ is "unbroken"). Anyone running CURRENT should be reading your message, but I'm a "belt and suspenders" type of guy on this sort of thing. Backing out of CURRENT and moving to 9-STABLE can be a REAL pain that will likely rapidly get worse as HEAD gets less and less frozen. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ 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"
