X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Message-ID:	<46283CAA.4000802@iki.fi>
Date:	Fri, 20 Apr 2007 07:08:10 +0300
From:	Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent:	Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: ANNOUNCE: Update of Binutils 2.17 uploaded
References:	<OF3817C62B DOT B12F4314-ON872572C2 DOT 00715646-872572C2 DOT 0071A425 AT seagate DOT com>
In-Reply-To:	<OF3817C62B.B12F4314-ON872572C2.00715646-872572C2.0071A425@seagate.com>
Reply-To:	djgpp-workers AT delorie DOT com

Gordon DOT Schumacher AT seagate DOT com kirjoitti:
> Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de> wrote on 04/19/2007 02:27:49
> PM:
> 
> # When binary distributions (aka NNNNNNb.zip) are produced it should be
> paid
> # attention that a possible generated dir file by the build proccess
> # should *not*
> # be included in the zip archive.  Nowadays GNU Makefiles usualy generate
> # one dir file during installation proccess if they can not find one.  This
> # implies that when the package is installed the djgpp dir file may be
> replaced
> # by this useless one.  Even worse if an dir file entry appears in the
> manifest
> # file for that binary archive.  This will remove the dir file from the
> /info
> # directory and the average user will no longer be able to read info docs.
> # This happened to me today when I deinstalled the old bnu217b.zip to
> reinstall
> # the new one.  It took me some time to understand why info stopped to work
> # as it should and what had happened  with my dir file.
> 
> Yes, I've fixed that in my new packages - that should be fixed in the new
> binutils.  (That was one of those "administrative details" that I mentioned
> :)
> 
> When I was first packaging I did not fully understand how the manifests
> were
> produced.  Now I have a script which does most of the grunt work for me.
> Once I get doschk integrated into it I will post it here.

One example is my scripts for generating GCC source and binary
packages. See scripts in gcc412s2.zip for details. The difference
however is that I didn't try to get GCC build process to work without
LFN support.

- Raw text -