LIGO Support Ticket 19341

Ticket Information
  Number:      admin 19341
  User:        carsten.aulbert@aei.mpg.de
  Email:       
  Status:      resolved
  Assigned To: psilord
Date: Fri, 29 May 2009 15:07:12 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: LIGO Building 7.2.3 on Debian Lenny amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 silica.cs.wisc.edu

Hi,

I'm just tryting to build condor 7.2.3 on Debian Lenny 64bit (fullport) and the build stops with this:

Setting up glibc-2.7-18-x86_64 ...
(see /build/condor-7.2.3/externals/build/log.glibc-2.7-18-x86_64)
glibc-2.7-18-x86_64: FAILED! (see /build/condor-7.2.3/externals/build/log.glibc-2.7-18-x86_64)
          define_iov_max="# undef IOV_MAX";                             \
        else                                                            \
          define_iov_max="# define IOV_MAX $iov_max";                   \
        fi;                                                             \
        sed -e "s/@FOPEN_MAX@/$fopen_max/"                              \
            -e "s/@FILENAME_MAX@/$filename_max/"                        \
            -e "s/@L_tmpnam@/20/"                               \
            -e "s/@TMP_MAX@/238328/"                            \
            -e "s/@L_ctermid@/9/"                               \
            -e "s/@L_cuserid@/9/"                               \
            -e "s/@define_IOV_MAX@/$define_iov_max/"                    \
            stdio-common/stdio_lim.h.in > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.h.new
/bin/sh scripts/move-if-change /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.h.new /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.h
rm -f /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.hT /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.dT /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.dt
touch /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/bits/stdio_lim.st
mawk -f scripts/gen-sorted.awk \
               -v subdirs='csu assert ctype locale intl catgets math setjmp signal stdlib stdio-common libio malloc string wcsmbs time dirent grp pwd posix io termios resource misc socket sysvipc gmon gnulib iconv iconvdata wctype manual shadow po argp crypt nss localedata timezone rt conform debug libidn dlfcn elf' \
               -v srcpfx='' \
               nptl/sysdeps/pthread/Subdirs sysdeps/unix/inet/Subdirs sysdeps/unix/Subdirs assert/Depend intl/Depend catgets/Depend stdlib/Depend stdio-common/Depend libio/Depend malloc/Depend string/Depend wcsmbs/Depend time/Depend posix/Depend iconvdata/Depend nss/Depend localedata/Depend rt/Depend debug/Depend > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/sysd-sorted-tmp
mawk: scripts/gen-sorted.awk: line 19: regular expression compile failed (bad class -- [], [^] or [)
/[^
mawk: scripts/gen-sorted.awk: line 19: syntax error at or near ]
mawk: scripts/gen-sorted.awk: line 19: runaway regular expression /, "", subd ...
make[2]: Leaving directory `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64'
make[2]: Entering directory `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64'
mawk -f scripts/gen-sorted.awk \
               -v subdirs='csu assert ctype locale intl catgets math setjmp signal stdlib stdio-common libio malloc string wcsmbs time dirent grp pwd posix io termios resource misc socket sysvipc gmon gnulib iconv iconvdata wctype manual shadow po argp crypt nss localedata timezone rt conform debug libidn dlfcn elf' \
               -v srcpfx='' \
               nptl/sysdeps/pthread/Subdirs sysdeps/unix/inet/Subdirs sysdeps/unix/Subdirs assert/Depend intl/Depend catgets/Depend stdlib/Depend stdio-common/Depend libio/Depend malloc/Depend string/Depend wcsmbs/Depend time/Depend posix/Depend iconvdata/Depend nss/Depend localedata/Depend rt/Depend debug/Depend > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/sysd-sorted-tmp
mawk: scripts/gen-sorted.awk: line 19: regular expression compile failed (bad class -- [], [^] or [)
/[^
mawk: scripts/gen-sorted.awk: line 19: syntax error at or near ]
mawk: scripts/gen-sorted.awk: line 19: runaway regular expression /, "", subd ...
rm -f /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.o; > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.o
rm -f /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.os; > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.os
rm -f /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.oS; > /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/stamp.oS
cd /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build && ar cruv libc.a `cat stamp.o`
: /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/libc.a
cd /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build && ar cruv libc_pic.a `cat stamp.os`
: /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/libc_pic.a
cd /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build && ar cruv libc_nonshared.a `cat stamp.oS`
: /build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/libc_nonshared.a
make[2]: *** No rule to make target `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/Versions.all', needed by `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build/abi-versions.h'.  Stop.
make[2]: Leaving directory `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/condor-7.2.3/externals/build/glibc-2.7-18-x86_64/glibc-2.7-18-x86_64-build'
make failed
ERROR: build_glibc-2.7-18-x86_64 returned: 1
ERROR: unable to build glibc-2.7-18-x86_64
ERROR: aborting
make: *** [/build/condor-7.2.3/externals/triggers/glibc-2.7-18-x86_64] Error 1

Since this is a build with the native compiler (which is gcc version 4.3.2 (Debian 4.3.2-1.1))
I don't know if that's related to this - so far we only used the 3.4 compiler for Etch.

The configure line is just:
./configure --prefix=/opt/condor --disable-rpm --enable-full-port
followed by 
make


Any idea what's breaking the build?

Cheers

Carsten

===========================================================================
Date of creation: Fri May 29  8:07:26 2009 (1243602449)
Subject: Actions

Assigned to psilord by roy
===========================================================================
Date of actions: Fri May 29  9:48:24 2009 (1243608504)
Date: Mon, 1 Jun 2009 16:26:44 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: roy <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

Hello,

I noticed an inconsistancy with your ticket:


On Fri, May 29, 2009 at 09:48:24AM -0500, roy wrote:
> From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
> 
> I'm just tryting to build condor 7.2.3 on Debian Lenny 64bit (fullport) and the build stops with this:

First you say you're compiling on Lenny, which is Debian 5.0.

> Since this is a build with the native compiler (which is gcc version 4.3.2 (Debian 4.3.2-1.1))

But then you say you're using Etch, which is Debian 5.0.

We only have clipped support for Debain 4.0. Does it work if you retry
your build on a debian 5.0 machine?

Thank you.

-pete

===========================================================================
Date mail was appended: Mon Jun  1 16:26:50 2009 (1243891610)
Subject: Actions

Status changed from open to pending by psilord
===========================================================================
Date of actions: Mon Jun  1 16:31:32 2009 (1243891892)
Date: Tue, 02 Jun 2009 07:39:18 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu

Hi Pete,

condor-admin response tracking system wrote:
> I noticed an inconsistancy with your ticket:

No :) Read below

>> I'm just tryting to build condor 7.2.3 on Debian Lenny 64bit (fullport) and the build stops with this:
> 
> First you say you're compiling on Lenny, which is Debian 5.0.

Yes, that's right.

> 
>> Since this is a build with the native compiler (which is gcc version 4.3.2 (Debian 4.3.2-1.1))
> 
> But then you say you're using Etch, which is Debian 5.0.

No (Etch would be 4.0) but this is just the version string of the gcc
(copy and pasted from gcc -v). Default compilers:
Etch: gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Lenny: gcc version 4.3.2 (Debian 4.3.2-1.1)
Squeeze: gcc version 4.3.3 (Debian 4.3.3-10) (but this is a moving target)
> 
> We only have clipped support for Debain 4.0. Does it work if you retry
> your build on a debian 5.0 machine?
> 

No, as that was what I was trying :)

Sorry for the confusion, maybe I should have written it more clearly.

Cheers

Carsten

===========================================================================
Date mail was appended: Tue Jun  2  0:39:38 2009 (1243921178)
Date: Mon, 8 Jun 2009 13:40:13 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: roy <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

Hello,

Ok, I'm looking at this ticket in earnest now.

Thank you.

-pete


===========================================================================
Date mail was appended: Mon Jun  8 13:40:19 2009 (1244486419)
Date: Mon, 8 Jun 2009 15:02:26 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: roy <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

Hello,

> From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
> 
> mawk: scripts/gen-sorted.awk: line 19: regular expression compile failed (bad class -- [], [^] or [)
> /[^
> mawk: scripts/gen-sorted.awk: line 19: syntax error at or near ]
> mawk: scripts/gen-sorted.awk: line 19: runaway regular expression /, "", subd ...

It occurs to me that mawk can't parse extended regular expression classes.

I fired up a build on our NMI machine and noticed that my build used
'gawk'--instead of 'mawk', to produce the glibc external.

Maybe you should install gawk on your machine and retry the build of Condor.
Make sure to rerun configure and validate that it finds gawk properly.

Thank you.

-pete

===========================================================================
Date mail was appended: Mon Jun  8 15:02:31 2009 (1244491352)
Subject: Actions

Status changed from open to pending by psilord
===========================================================================
Date of actions: Mon Jun  8 15:02:37 2009 (1244491357)
Date: Tue, 09 Jun 2009 14:07:01 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 gypsum.cs.wisc.edu

Hi Pete,

condor-admin response tracking system wrote:
> It occurs to me that mawk can't parse extended regular expression classes.
> 
> I fired up a build on our NMI machine and noticed that my build used
> 'gawk'--instead of 'mawk', to produce the glibc external.
> 
> Maybe you should install gawk on your machine and retry the build of Condor.
> Make sure to rerun configure and validate that it finds gawk properly.

I've tried again and after many more tweaks I can compile condor fine
locally (with default gcc-4.3). For reference I needed the following
packages as build-dependencies:

gawk byacc bison autoconf automake libncurses5-dev
flex libcurl4-openssl-dev libx11-dev

Questions regarding this:

* Condor is building openssl itself, why do I need to have
openssl-development stuff installed as well?

* You might want to put ncurses-dev into the README file as tgentent is
being referenced.

I'm not sure if both bison and byacc are needed, but byacc alone is not
enough

I think you can close this but if you want to, but may I ask a final
question:

Before Condor is built, you are building libkrb5, openssl, postgresql,
globus4.2, ... would it be possible, to use the system installed
versions instead?

Cheers

Carsten

===========================================================================
Date mail was appended: Tue Jun  9  7:07:13 2009 (1244549234)
Date: Tue, 09 Jun 2009 14:30:00 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 gypsum.cs.wisc.edu

Hi again

Carsten Aulbert wrote:
> Before Condor is built, you are building libkrb5, openssl, postgresql,
> globus4.2, ... would it be possible, to use the system installed
> versions instead?
> 

stupid me, I'm just seeing the --with-* switches for configure... we
might play around with those a bit.

Cheers

Carsten

===========================================================================
Date mail was appended: Tue Jun  9  7:30:17 2009 (1244550618)
Date: Tue, 9 Jun 2009 10:11:35 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: condor-admin response tracking system <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

On Tue, Jun 09, 2009 at 07:30:17AM -0500, condor-admin response tracking system wrote:
> stupid me, I'm just seeing the --with-* switches for configure... we
> might play around with those a bit.

There is also --with-proper, which will use system libraries as a
rule, but I'm not entirely sure how it will react with a full port of
Condor.

Thank you.

-pete

===========================================================================
Date mail was appended: Tue Jun  9 10:11:40 2009 (1244560300)
Date: Tue, 09 Jun 2009 17:18:03 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu

Hi

condor-admin response tracking system wrote:
> There is also --with-proper, which will use system libraries as a
> rule, but I'm not entirely sure how it will react with a full port of
> Condor.

Henning just did that and it seems it won't build the special glibc
anymore thus possible no standard universe support :(

Cheers

Carsten

===========================================================================
Date mail was appended: Tue Jun  9 10:18:15 2009 (1244560697)
Date: Tue, 9 Jun 2009 10:25:44 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: condor-admin response tracking system <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

On Tue, Jun 09, 2009 at 07:07:13AM -0500, condor-admin response tracking system wrote:
> gawk byacc bison autoconf automake libncurses5-dev
> flex libcurl4-openssl-dev libx11-dev

Ok, I added these to the readme file. I've noticed that over time, it is
becoming a crap shoot that a random linux distro includes good tools used for
development.

> * Condor is building openssl itself, why do I need to have
> openssl-development stuff installed as well?

How did your build die in needing openssl? It may be that a different
external required it and died. Or was it the Condor source itself that
required it and died?

> I think you can close this but if you want to, but may I ask a final
> question:

I answered that in the other email.

If you agree that this ticket is resolved, you did build Condor in the end,
then I shall resolve it.

Thank you.

-pete

===========================================================================
Date mail was appended: Tue Jun  9 10:25:46 2009 (1244561146)
Date: Tue, 9 Jun 2009 10:27:23 -0500
From: Peter Keller <psilord__AT__cs.wisc.edu>
To: condor-admin response tracking system <condor-admin__AT__cs.wisc.edu>
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage

On Tue, Jun 09, 2009 at 10:18:15AM -0500, condor-admin response tracking system wrote:
> Hi
> 
> condor-admin response tracking system wrote:
> > There is also --with-proper, which will use system libraries as a
> > rule, but I'm not entirely sure how it will react with a full port of
> > Condor.
> 
> Henning just did that and it seems it won't build the special glibc
> anymore thus possible no standard universe support :(

Yeah, I'm not surprised about that at all. --with-propoer was really
created for a purpose which didn't mesh very well with building out own glibc.
You may have to specify all of the system stuff with the individual --with-*
arguments. 

(Even though the other thread said I was going to resolve this, I will now
wait for a direct response on this ticket stating you'd like to resolve it
since you asked this question.)

Thank you.

-pete

===========================================================================
Date mail was appended: Tue Jun  9 10:27:28 2009 (1244561248)
Date: Tue, 09 Jun 2009 17:29:42 +0200
From: Carsten Aulbert <carsten.aulbert__AT__aei.mpg.de>
To: condor-admin__AT__cs.wisc.edu
Subject: Re: [condor-admin #19341] LIGO Building 7.2.3 on Debian Lenny
 amd64 fails at glibc stage
X-Enigmail-Version: 0.95.7
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu

Hi

condor-admin response tracking system wrote:
>> * Condor is building openssl itself, why do I need to have
>> openssl-development stuff installed as well?
> 
> How did your build die in needing openssl? It may be that a different
> external required it and died. Or was it the Condor source itself that
> required it and died?

openssl compiling worked fine, it was at a later stage that something
needed libssl and did not find it. I can try to trace the steps back to
re-discover that again, i.e. the error was similar to "-lssl not found"

> 
>> I think you can close this but if you want to, but may I ask a final
>> question:
> 
> I answered that in the other email.
> 
> If you agree that this ticket is resolved, you did build Condor in the end,
> then I shall resolve it.
> 

Yes, please, thanks a lot for the input!

Cheers

Carsten

===========================================================================
Date mail was appended: Tue Jun  9 10:29:52 2009 (1244561392)
Subject: Actions

Ticket resolved by psilord
===========================================================================
Date of actions: Tue Jun  9 10:48:57 2009 (1244562537)