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

Bug#159570: glibc: Please document/update building process



On Wed, Sep 04, 2002 at 11:51:42AM +0200, Marcelo E. Magallon wrote:

>  > This directory contains the files needed to build glibc for the
>  > Debian GNU/Linux and GNU/Hurd distributions.

>  > To build this package, you'll need this `debian' directory, and
>  > `glibc-VERSION.tar.gz', and `glibc-linuxthreads-LTVERSION.tar.gz'
>  > (the VERSIONS need not match). Put them all in a directory called
>  > `glibc-VERSION', and make sure that the `debian/rules',
>  > `debian/changelog', and `debian/sysdeps/config.mk' refer
>  > correctly to VERSION.  Then, you can run dpkg-buildpackage, which
>  > will automatically unpack the tarballs, and start the build.

>  That's probably correct.  I have the feeling there's something
>  missing there, like "if you want to package a newer version" or
>  something like that.  I mean, I'm looking at the debian sources,
>  I'd expect those files to be there and be the correct ones.

I'll think about this - The problem is that updating to a newer
version can be hairy because of all the patches we apply.  Essentially
all that's needed is for some to bump the usual Debian verison
numbers, and one file - but that would all show up in grepping for the
current version.  

>  > Compiling the GNU C library yourself requires a lot of resources.

>  This sounds a bit outdated. 

Already updated for the next version - I did this a couple days ago
when I read the README file. =)

>  I wasn't paying attention, but one of my boxes (PIII-500) chewed
>  away for about 40 minutes or so.  Updating the trivia would be
>  nice, not required, but nice.

The log files in the next uploaded version include timestamps for
collecting this trivia. =)

>  > For Linux, you will need at least the kernel-headers for the
>  > specific kernel version required for your machine's architecture.
>  > These are specified in the `debian/sysdeps/linux.mk' file, and
>  > can be overridden by exporting the environment variable
>  > LINUX_SOURCE set to the path to the desired kernel.

>  That's ok.  "package" is probably missing between "kernel-headers"
>  and "for" in the first line.  Then again, it's probably not and the
>  hyphen shouldn't be there in the first place.

Hyphen removed.  Any kernel sources work fine.

>  Now to the bug :-)

>  Can you please document the (interesting) debian/rules targets?
>  unpack at least.  It takes 10 seconds to figure out that
>  debian/rules unpack will unpack the sources after looking at
>  debian/rules, but my first try was actually debian/README.

I'm probably going to hold off on this - It's not clear yet whether
the dpkg-source v2 will be flexible enough for glibc.  If it is, we'll
probably move to completely-standard ways of doing stuff.  Failing
that, it would make sense for us to use the dbs package or something.

Thanks for the report, though.

-- 
At last you cry out in anguish: "Why me?"
God answers: "Why not?"
 - Sheldon Kopp



Reply to: