Re: Bug#39227: apt: archtable does not support hurd
On Wed, 9 Jun 1999 brinkmd@debian.org wrote:
> the "gcc --print-libgcc-file-name" + archtable trick obviously doesn't work
> on the Hurd without changes.
Why shouldn't it? What does --print-libgcc-file-name return on the hurd?
> I suggest to try:
>
> "dpkg --print-installation-architecture" if not cross-compiling and dpkg
> is available, which should always be correct, and is the only sensible
> way without duplicating "arbitray" conversion code from dpkg.
There are two things being set here, the first is the arch string for dpkg
and the next is the byte sizes for the MD5 code, it is important to not
munge up either.
> For cross compilation, the gcc trick is a good approximation, but please
> don't strip off -whatever, but check if it is linux or gnu, or even better,
> use full gnu system type names in the archtable:
>
> i386-linux i386 i486
> i386-gnu hurd-i386 i486
What you really need here is a seperate setting that indicates what the OS
is, it would be nicer than trying to munge the arch string. What could be
done is to write a detection rule for hurd/linux/etc and have that create
a sepeare entry in config.h, it could then munge it internally to generate
the correct test for whatever todays arch/system standard is.
I like having the arch transforms as a seperate operation from system type
transforms, that seems to make more sense.
> BTW, can pthreads be made optional? It seems apt-get can be build without
> pthread, and it would be good for configure just to disable components that
> require pthread instead of bailing out completely (reason is that the Hurd
> does not have pthreads implemented of course. We wouldn't miss the fancy
> gui right now, but we miss the apt-get tool a lot).
Yes, that test could be removed from configure. As long as the C library
does not declare it has pthread support by defing _POSIX_THREADS then
everything will be OK. The GUI library does/did/might require pthreads but
that isn't compiled by default anymore
I'm not terribly good with hacking configure/autoconf, if you could
implement a good patch for the system type that would be very nice. Sounds
like all that is needed is to save the -foo part after the arch string and
write that to the config file.
Jason
Reply to: