[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can we upload binaries using libc6 to hamm yet?

On Apr 23, Helmut Geyer wrote
> jdassen@wi.leidenuniv.nl (J.H.M.Dassen) writes:
> > On Apr 23, Thomas Koenig wrote
> > > [Warning - question from ignorance]
> > > 
> > > On a system which has both libc5 and libc6 installed, I assume that
> > > some options are needed to select libc5.  Where do these go?
> > > 
> > > Or do I need a second machine?
> > 
> > [Warning: I'm new at this too]

This is why I was concerned about bringing this issue up now.  I don't
want a lot of developers to get sucked in and get distracted from
releasing bo.

> > AFAIK you can install both the libc5 and the libc6 runtime packages on the
> > same machine; however, libc5-dev and libc6-dev cannot be installed
> > simultaneously.


> > Some ways that might deal with this:
> > - keep both at hand as .deb files, and install the one you need

This is what I had intended.  Yes, I know it will be a pain to switch
development environments between libc5 and libc6, but it will only be
inflicted on developers.  That pain may also be a good thing in that
it may encourage developers to concentrate on libc6.

> > - fiddle with unpacking libc6-dev in /usr/local (dpkg-deb), and use modified
> >   PATH when compiling. This approach was taken in the a.out->ELF (libc4 ->
> >   libc5) transition for test compiles.
> > - chroot()ed environment for libc6 development.
> > 
> There is a different approach suggested by the libc6 developer:
> You need a different gcc (or at least a different specs file) to
> compile. At this time, the new gcc package does not support compiling
> using libc5. This could be generated, however.

This is not true.  You can use command-line options to get the new gcc
to do the right thing.  In other words, we only need one gcc package.

> using the suggestions from ld.so 1.9.2 or the GNU libc installation
> info on linux, it would be possible to have both libc-dev packages
> installed, using 'gcc -b i486-linuxlibc5' as crosscompiler.
> We would need at least the following new packages:
>  - a modified gcc package to inlcude the crosscompiler for libc5

See above.

>  - a modified libc5 package using the */libc5-compat directories

This is already planned.

>  - a modified libc5-dev package using the */libc5-compat directories.

I hadn't planned on this, but I don't see a big problem with it.
Where would the include files go?  I know some people won't want a
/usr/i486-linuxlibc5 hierarchy.

> The second and third part would be needed for any library used in the
> package.
> Please read my other mail concerning this as well.
> As for the deb-files approach, I'm dead against it.
> I think, it would be very hard to install/remove 10-20 debian packages
> just to compile a bugfix for the stable tree.

David Engel                        ODS Networks
david@sw.ods.com                   1001 E. Arapaho Road
(972) 234-6400                     Richardson, TX  75081

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: