Re: [Condor-devel] debian support

[guillaume pernot <gpernot@xxxxxxxxxxx>]

hi,

Le mardi 24 octobre 2006 18:49, Peter Keller a écrit :
> On Tue, Oct 24, 2006 at 05:48:05PM +0200, guillaume pernot wrote:
> > gconv_open.c: In function '__gconv_open':
> > gconv_open.c:186: error: invalid lvalue in assignment
> 
> > hum, long is the road :(
> 
> I remember that error... :(
> 
> You might be able to patch the glibc to fix whatever problem it had
> to compile under that compiler, but that can be a dangerous road of
> having to perform many fixes and being *very* careful you didn't
> break anything.
> 
> In general, when we port Condor to a specific linux distribution, we
> strive to use the compiler which comes with the installation of that
> distribution. However, recent evolution for glibcs and compilers have
> made that very difficult to do and as a result, we've been having to
> use older compilers than we desire for distributions like RHEL3. This
> is because it was cheaper in man hours to use an older compiler than it
> was to perform a full port.
> 
> For the majority of our users, this is ok, since we can link with the
> recent compiler on the machine (but in reality things like C++ STL
> templates break, however 99% of our users happen not to use the STL).
> 
> So, if you want the distribution of Condor to be compilable on the
> debian machine, it might be better to just do a clipped port of Condor
> (set IS_CLIPPED to YES in the LINUX_DEBIAN.cf config file) instead.
> People would still gain all of the functionality of Condor, except the
> standard universe. Then, if people wanted the standard universe, they
> could download the RHEL3 distribution and use that.

my aim is getting condor into debian main archive, so that it will end up in 
ubuntu, and then widely spread to linux workstations.

(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=233482)

using rhel3 tarball is not a debian-acceptable solution...

there is still the source code availability problem, though. but i think (hum, 
i hope) that this should be fixed by the days we have a fully validated 
gcc-4.0.3-compiled condor.

> 
> This is of course, not ideal. But it takes so long to perform and
> validate full ports of Condor to arbitrary distributions, we ended up
> in this scenario.

i'll try to make is as good as possible... i'm starting with patching glibc so 
that it compiles with gcc-4.0.3. i will see where that may lead...

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