From dam at opencsw.org Mon Aug 2 13:19:24 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Mon, 2 Aug 2010 13:19:24 +0200 Subject: [csw-buildfarm] Updating the current/ buildfarm to current. Message-ID: <2498E80F-7209-4C2E-BC6E-69AAD5B230CB@opencsw.org> Hi, I am updating the current buildfarm to current/ now. Please stand by. Best regards -- Dago From dam at opencsw.org Fri Aug 6 09:23:39 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Fri, 6 Aug 2010 09:23:39 +0200 Subject: [csw-buildfarm] Updating current/ now Message-ID: Hi, I am updating the current-servers to current/, please stand by! Sorry for the inconvenience -- Dago From maciej at opencsw.org Thu Aug 12 14:26:59 2010 From: maciej at opencsw.org (Maciej (Matchek) Blizinski) Date: Thu, 12 Aug 2010 13:26:59 +0100 Subject: [csw-buildfarm] [csw-maintainers] Change of compiler location on OpenCSW buildfarm In-Reply-To: References: <2BA946A2-9D40-4D96-8767-E96AE482CF14@baltic-online.de> Message-ID: No dia 2 de Agosto de 2010 12:20, Dagobert Michelsen escreveu: > Hi, > > with the deprecation of Solaris 8 I will change the compiler pathes to a > more > regular scheme. Especially the Sun Studio 12 compiler will be linked to > /opt/SUNWspro and gar.conf.mk will be adjusted to the new location. This > allows for more sane pathes in applications that record the path (like > Perl and Ruby). I plan to make the change this evening (in about 5 hours). > The current locations /opt/studio/SOS12/SUNWspro will stay intact, though. I think I've updated GAR sources, and I still see the following in gar.conf.mk: SOS12_CC_HOME ?= /opt/studio/SOS12/SUNWspro ...which makes the compilation fail on testing9x, because the /opt/studio/SOS12 path is missing. From dam at opencsw.org Thu Aug 12 14:37:06 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Thu, 12 Aug 2010 14:37:06 +0200 Subject: [csw-buildfarm] [csw-maintainers] Change of compiler location on OpenCSW buildfarm In-Reply-To: References: <2BA946A2-9D40-4D96-8767-E96AE482CF14@baltic-online.de> Message-ID: Hi Maciej, Am 12.08.2010 um 14:26 schrieb Maciej (Matchek) Blizinski: > No dia 2 de Agosto de 2010 12:20, Dagobert Michelsen > escreveu: >> Hi, >> >> with the deprecation of Solaris 8 I will change the compiler pathes >> to a >> more >> regular scheme. Especially the Sun Studio 12 compiler will be >> linked to >> /opt/SUNWspro and gar.conf.mk will be adjusted to the new location. >> This >> allows for more sane pathes in applications that record the path >> (like >> Perl and Ruby). I plan to make the change this evening (in about 5 >> hours). >> The current locations /opt/studio/SOS12/SUNWspro will stay intact, >> though. > > I think I've updated GAR sources, and I still see the following in > gar.conf.mk: > > SOS12_CC_HOME ?= /opt/studio/SOS12/SUNWspro > > ...which makes the compilation fail on testing9x, because the > /opt/studio/SOS12 path is missing. Ah, I see. This is correct as it is just a default. The machine-specific setting is in /etc/opt/csw/garrc which was missing on testing9x. Everything should be fine now, you can check with your project with gmake ccenv Best regards -- Dago From rupert at opencsw.org Fri Aug 13 19:53:55 2010 From: rupert at opencsw.org (rupert THURNER) Date: Fri, 13 Aug 2010 19:53:55 +0200 Subject: [csw-buildfarm] gmake replatforms not working? Message-ID: after updating gar, when building the new version of mercurial i got: build9s gmake replatforms /opt/studio/SOS12/SUNWspro/bin/cc -G -m32 -xarch=v8 -norunpath -L/opt/csw/lib -xO3 -m32 -xarch=v8 -xnorunpath -I/opt/csw/include build/temp.solaris-2.9-sun4u-2.6/mercurial/base85.o -L/opt/csw/lib -lpython2.6 -o build/lib.solaris-2.9-sun4u-2.6/mercurial/base85.so unable to execute /opt/studio/SOS12/SUNWspro/bin/cc: No such file or directory error: command '/opt/studio/SOS12/SUNWspro/bin/cc' failed with exit status 1 gmake[2]: *** [build-work/solaris9-sparc/build-isa-sparcv8/mercurial-1.6.2/setup.py] Error 1 gmake[2]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' gmake[1]: *** [merge-isa-sparcv8] Error 2 gmake[1]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' gmake: *** [platforms] Error 2 From bonivart at opencsw.org Thu Aug 26 18:02:31 2010 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 26 Aug 2010 18:02:31 +0200 Subject: [csw-buildfarm] Please install CSWsocat on build9x|s Message-ID: Thanks. -- /peter From bwalton at opencsw.org Thu Aug 26 18:34:40 2010 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 26 Aug 2010 12:34:40 -0400 Subject: [csw-buildfarm] Please install CSWsocat on build9x|s In-Reply-To: References: Message-ID: <1282840471-sup-7463@pinkfloyd.chass.utoronto.ca> Excerpts from Peter Bonivart's message of Thu Aug 26 12:02:31 -0400 2010: In progress. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From yann at pleiades.fr.eu.org Mon Aug 30 23:13:41 2010 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Mon, 30 Aug 2010 23:13:41 +0200 Subject: [csw-buildfarm] Please install libsocks Message-ID: <4C7C1F05.80008@pleiades.fr.eu.org> Hi, Could you please install the libsocks package on the buildfarm ? I need it to be enable to add socks5 support to lftp: [...] checking whether to use NLS... yes checking where the gettext function comes from... external libintl checking how to link with libintl... /opt/csw/lib/libintl.so -R/opt/csw/lib checking for main in -lsocks5... no configure: error: cannot find -lsocks5 library Thanks in advance. Yann From bwalton at artsci.utoronto.ca Tue Aug 31 01:31:27 2010 From: bwalton at artsci.utoronto.ca (Ben Walton) Date: Mon, 30 Aug 2010 19:31:27 -0400 Subject: [csw-buildfarm] Please install libsocks In-Reply-To: <4C7C1F05.80008@pleiades.fr.eu.org> References: <4C7C1F05.80008@pleiades.fr.eu.org> Message-ID: <1283211044-sup-8014@pinkfloyd.chass.utoronto.ca> Excerpts from Yann Rouillard's message of Mon Aug 30 17:13:41 -0400 2010: > Could you please install the libsocks package on the buildfarm ? > I need it to be enable to add socks5 support to lftp: Doing this now. -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From dam at opencsw.org Tue Aug 31 08:44:55 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 31 Aug 2010 08:44:55 +0200 Subject: [csw-buildfarm] what happened with libsigsegv.so.0? gawk is not working In-Reply-To: <20100726133026.79723f98@deb0> References: <20100726133026.79723f98@deb0> Message-ID: Hi T?r?k, Am 26.07.2010 um 12:30 schrieb T?r?k Edwin: > My buildbot failed this morning with this message: > ld.so.1: gawk: fatal: libsigsegv.so.0: open failed: No such file or > directory This is very strange. A couple of weeks ago I redid libsigsegv and missed the old .so.0, but fixed that a day later. The gawk on current10s seems to work fine for me, but I took the opportunity to update all current* machines anyway. Please verify the date of the build and let me know if you encounter any more problems. Sorry for the invonvenience -- Dago From rupert at opencsw.org Tue Aug 31 19:04:12 2010 From: rupert at opencsw.org (rupert THURNER) Date: Tue, 31 Aug 2010 19:04:12 +0200 Subject: [csw-buildfarm] python not using the new SOS12 path ... Message-ID: hi, while trying to release a new version of mercurial it bailed out with: /opt/studio/SOS12/SUNWspro/bin/cc -G -m32 -xarch=v8 -norunpath -L/opt/csw/lib -xO3 -m32 -xarch=v8 -xnorunpath -I/opt/csw/include build/temp.solaris-2.9-sun4u-2.6/mercurial/base85.o -L/opt/csw/lib -lpython2.6 -o build/lib.solaris-2.9-sun4u-2.6/mercurial/base85.so unable to execute /opt/studio/SOS12/SUNWspro/bin/cc: No such file or directory error: command '/opt/studio/SOS12/SUNWspro/bin/cc' failed with exit status 1 gmake[2]: *** [build-work/solaris9-sparc/build-isa-sparcv8/mercurial-1.6.3/setup.py] Error 1 gmake[2]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' gmake[1]: *** [merge-isa-sparcv8] Error 2 gmake[1]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' gmake: *** [platforms] Error 2 it seems the python package installed on the buildserver has the old path in it, and setuptools tries to use it while building mercurial. what can we do to fix this? kr, rupert. From dam at opencsw.org Tue Aug 31 19:12:41 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 31 Aug 2010 19:12:41 +0200 Subject: [csw-buildfarm] python not using the new SOS12 path ... In-Reply-To: References: Message-ID: <615524DF-DEEC-4395-83C6-869F87B8EAD3@opencsw.org> Hi Rupert, Am 31.08.2010 um 19:04 schrieb rupert THURNER: > while trying to release a new version of mercurial it bailed out with: > > /opt/studio/SOS12/SUNWspro/bin/cc -G -m32 -xarch=v8 -norunpath > -L/opt/csw/lib -xO3 -m32 -xarch=v8 -xnorunpath -I/opt/csw/include > build/temp.solaris-2.9-sun4u-2.6/mercurial/base85.o -L/opt/csw/lib > -lpython2.6 -o build/lib.solaris-2.9-sun4u-2.6/mercurial/base85.so > unable to execute /opt/studio/SOS12/SUNWspro/bin/cc: No such file or > directory > error: command '/opt/studio/SOS12/SUNWspro/bin/cc' failed with exit > status 1 > gmake[2]: *** [build-work/solaris9-sparc/build-isa-sparcv8/ > mercurial-1.6.3/setup.py] > Error 1 > gmake[2]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' > gmake[1]: *** [merge-isa-sparcv8] Error 2 > gmake[1]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' > gmake: *** [platforms] Error 2 > > it seems the python package installed on the buildserver has the old > path in it, and setuptools tries to use it while building mercurial. > what can we do to fix this? We kindle ask Maciej to just respin Python, which should fix the problem. Best regards -- Dago From maciej at opencsw.org Tue Aug 31 19:19:28 2010 From: maciej at opencsw.org (Maciej (Matchek) Blizinski) Date: Tue, 31 Aug 2010 18:19:28 +0100 Subject: [csw-buildfarm] python not using the new SOS12 path ... In-Reply-To: <615524DF-DEEC-4395-83C6-869F87B8EAD3@opencsw.org> References: <615524DF-DEEC-4395-83C6-869F87B8EAD3@opencsw.org> Message-ID: No dia 31 de Agosto de 2010 18:12, Dagobert Michelsen escreveu: > Hi Rupert, > > Am 31.08.2010 um 19:04 schrieb rupert THURNER: >> >> while trying to release a new version of mercurial it bailed out with: >> >> /opt/studio/SOS12/SUNWspro/bin/cc -G -m32 -xarch=v8 -norunpath >> -L/opt/csw/lib -xO3 -m32 -xarch=v8 -xnorunpath -I/opt/csw/include >> build/temp.solaris-2.9-sun4u-2.6/mercurial/base85.o -L/opt/csw/lib >> -lpython2.6 -o build/lib.solaris-2.9-sun4u-2.6/mercurial/base85.so >> unable to execute /opt/studio/SOS12/SUNWspro/bin/cc: No such file or >> directory >> error: command '/opt/studio/SOS12/SUNWspro/bin/cc' failed with exit status >> 1 >> gmake[2]: *** >> [build-work/solaris9-sparc/build-isa-sparcv8/mercurial-1.6.3/setup.py] >> Error 1 >> gmake[2]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' >> gmake[1]: *** [merge-isa-sparcv8] Error 2 >> gmake[1]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk' >> gmake: *** [platforms] Error 2 >> >> it seems the python package installed on the buildserver has the old >> path in it, and setuptools tries to use it while building mercurial. >> what can we do to fix this? > > We kindle ask Maciej to just respin Python, which should fix the problem. Yes, I'd like a kindle. ;-) OK, kicking off Python reroll. From bwalton at opencsw.org Tue Aug 31 20:53:45 2010 From: bwalton at opencsw.org (Ben Walton) Date: Tue, 31 Aug 2010 14:53:45 -0400 Subject: [csw-buildfarm] ipv6 on buildfarm Message-ID: <1283280778-sup-2920@pinkfloyd.chass.utoronto.ca> Hi Rupert, IPv6 is enabled for lo0 on current9x but not on current9s. This could account for the differences you're seeing. I'll defer to Dago as to what the preferred solution is (disable on 9x or enable on 9s). Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From rupert at opencsw.org Tue Aug 31 21:08:31 2010 From: rupert at opencsw.org (rupert THURNER) Date: Tue, 31 Aug 2010 21:08:31 +0200 Subject: [csw-buildfarm] ipv6 on buildfarm In-Reply-To: <1283280778-sup-2920@pinkfloyd.chass.utoronto.ca> References: <1283280778-sup-2920@pinkfloyd.chass.utoronto.ca> Message-ID: thanks for the info, i built apr without tests on current9s and sumbitted it, as it had only the ipv6 related test failing. rupert. On Tue, Aug 31, 2010 at 20:53, Ben Walton wrote: > > Hi Rupert, > > IPv6 is enabled for lo0 on current9x but not on current9s. ?This could > account for the differences you're seeing. ?I'll defer to Dago as to > what the preferred solution is (disable on 9x or enable on 9s). > > Thanks > -Ben > -- > Ben Walton > Systems Programmer - CHASS > University of Toronto > C:416.407.5610 | W:416.978.4302 > > From rupert at opencsw.org Tue Aug 31 21:11:15 2010 From: rupert at opencsw.org (rupert THURNER) Date: Tue, 31 Aug 2010 21:11:15 +0200 Subject: [csw-buildfarm] ipv6 on buildfarm In-Reply-To: References: <1283280778-sup-2920@pinkfloyd.chass.utoronto.ca> Message-ID: ben, could you install this version of apr on the buildfarm now? at least the on build9x as this one is lacking the uuid functions which then breaks the apr-util tests. then i could rebuild apr-util as well. rupert. On Tue, Aug 31, 2010 at 21:08, rupert THURNER wrote: > thanks for the info, i built apr without tests on current9s and > sumbitted it, as it had only the ipv6 related test failing. > > rupert. > > > On Tue, Aug 31, 2010 at 20:53, Ben Walton wrote: >> >> Hi Rupert, >> >> IPv6 is enabled for lo0 on current9x but not on current9s. ?This could >> account for the differences you're seeing. ?I'll defer to Dago as to >> what the preferred solution is (disable on 9x or enable on 9s). >> >> Thanks >> -Ben >> -- >> Ben Walton >> Systems Programmer - CHASS >> University of Toronto >> C:416.407.5610 | W:416.978.4302 >> >> > From rupert at opencsw.org Tue Aug 31 21:23:16 2010 From: rupert at opencsw.org (rupert THURNER) Date: Tue, 31 Aug 2010 21:23:16 +0200 Subject: [csw-buildfarm] ipv6 on buildfarm In-Reply-To: References: <1283280778-sup-2920@pinkfloyd.chass.utoronto.ca> Message-ID: as i run out of time, i rebuilt apr-util on current9x without tests as well, and submitted it. the tests on current9s were fine so i do not expect test failures other than caused by configuration differences. as soon as both new packages, apr and apr-util, are installed on the buildfarm, we may tackle apache2. thanks for your quick help. rupert. On Tue, Aug 31, 2010 at 21:11, rupert THURNER wrote: > ben, could you install this version of apr on the buildfarm now? at > least the on build9x as this one is lacking the uuid functions which > then breaks the apr-util tests. then i could rebuild apr-util as well. > > rupert. > > On Tue, Aug 31, 2010 at 21:08, rupert THURNER wrote: >> thanks for the info, i built apr without tests on current9s and >> sumbitted it, as it had only the ipv6 related test failing. >> >> rupert. >> >> >> On Tue, Aug 31, 2010 at 20:53, Ben Walton wrote: >>> >>> Hi Rupert, >>> >>> IPv6 is enabled for lo0 on current9x but not on current9s. ?This could >>> account for the differences you're seeing. ?I'll defer to Dago as to >>> what the preferred solution is (disable on 9x or enable on 9s). >>> >>> Thanks >>> -Ben >>> -- >>> Ben Walton >>> Systems Programmer - CHASS >>> University of Toronto >>> C:416.407.5610 | W:416.978.4302 >>> >>> >> > From edwin at clamav.net Tue Aug 31 11:03:04 2010 From: edwin at clamav.net (=?UTF-8?B?VMO2csO2aw==?= Edwin) Date: Tue, 31 Aug 2010 12:03:04 +0300 Subject: [csw-buildfarm] what happened with libsigsegv.so.0? gawk is not working In-Reply-To: References: <20100726133026.79723f98@deb0> Message-ID: <20100831120304.67cf9017@deb0> On Tue, 31 Aug 2010 08:44:55 +0200 Dagobert Michelsen wrote: > Hi T?r?k, > > Am 26.07.2010 um 12:30 schrieb T?r?k Edwin: > > My buildbot failed this morning with this message: > > ld.so.1: gawk: fatal: libsigsegv.so.0: open failed: No such file or > > directory > > This is very strange. A couple of weeks ago I redid libsigsegv and > missed > the old .so.0, but fixed that a day later. The gawk on current10s > seems to work fine for me, but I took the opportunity to update all > current* machines anyway. Please verify the date of the build and let > me know if you encounter any more problems. Everything is working now, thanks. Best regards, --Edwin