Re: [Condor-devel] debian support

[guillaume pernot <gpernot@xxxxxxxxxxx>]

hi,

Le mardi 24 octobre 2006 16:10, Peter Keller a écrit :
> On Tue, Oct 24, 2006 at 11:17:58AM +0200, guillaume pernot wrote:
> 
> What version of glibc is used on these machines and what revisions of
> gcc come on them? The version of glibc that Condor uses for its standard
> universe codes is very exact and changing that revision will force a
> full port of Condor to the new OS revision.

on ubuntu/dapper, this is glibc 2.3.6, that doesn't compile cleanly with gcc 
4.0.3. debian's glibc maintainer compiles it using gcc 3.4.

> 
> A full port of Condor generally means deep magic must be performed in
> the condor_ckpt and condor_syscall_lib directories. For example, stat() 
> and its various implementations might have changed, objects might have
> moved around suspiciously in the archive, functions we should trap could
> have changed/been added, the extraction pattern denoted in the Imakefile
> might have changed. It is a big deal to verify that a new glibc works
> properly with respect to Condor since it in generally unknown what changed
> in detail between the glibc you start with and the glibc to want to use.
> 
> In addition, the default gcc a machine has might affect the port as well
> since we must ship along the internal libraries of gcc, and those might
> also have changed.
> 
> Sometimes a full port just takes a week or two, sometimes 12-16 weeks. It
> really depends on the particular circumstances between Condor and the
> target machine in question.

my next try is to build the shipped glibc 2.3.2.27.9.7 with gcc-4.0. i think 
this is a more circumspect approach than to deal with both glibc and gcc 
ports.

> 
> I'd recommend running the entire condor test suite (both stduniv and
> other tests) if you go down this path (or really, if you do any patching
> of Condor). 

ok, i will.

> Of course, I can help if you need it. 

if i find myself locked at some point, any help will be appreciated ;)

regards,
-- 
guillaume pernot
http://www.praksys.org - Midi-Pyrénées et Aquitaine
Membre du réseau Libre Entreprise
GPG fingerprint : D356 5318 CE52 64C9 0CEF