X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Authenticated: #27081556
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
To: djgpp-workers AT delorie DOT com
Subject: Re: gcc installation path issue
Date: Sun, 9 Apr 2006 16:51:06 +0200
User-Agent: KMail/1.8.2
References: <200604071846 DOT 37701 DOT juan DOT guerrero AT gmx DOT de> <4438ED98 DOT 7010906 AT iki DOT fi>
In-Reply-To: <4438ED98.7010906@iki.fi>
Cc: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604091651.07112.juan.guerrero@gmx.de>
X-Y-GMX-Trusted: 0
Reply-To: djgpp-workers AT delorie DOT com

Am Sonntag, 9. April 2006 13:18 schrieb Andris Pavenis:
> Juan Manuel Guerrero wrote:
> > While installing gcc410b.zip I have noticed that certain headers go into
> > /lib/gcc/djgpp/4.1.0/include/ssp while the vast mayority of the headers
> > are installed into /lib/gcc/djgpp/4.10/include. The first location is not
> > SFN clean. Giving to gcc the command --print-search-path shows that the
> > first path ist never taken into account. Of course it is easy to manualy
> > move the /ssp dir into the /lib/gcc/djgpp/4.10/include dir but it may
> > nice if this could be fixed in the next release.
> 
> Fixed it by patching additionally libssp/Makefile.am and libssp/configure.ac.
> Is it worth to upload fixed archives of gcc-4.1.0?
> 
> Nobody else noticed it. Perhaps very few people uses DJGPP on plain DOS
> any more...
> 
> Andris

IMHO this argument is not completly valid. The essential issue is not that the
pathname is not SFN clean, the essential issue is that the headers are installed
in to different locations (/lib/gcc/djgpp/4.1.0/include/ssp and  /lib/gcc/djgpp/4.10/include)
and that the first location does not appear in the search path of the compiler
so all headers there are invisible. If this produces no harm then the headers
are useless and may be omitted.
My intention was not to ask for a new release of gcc410{bs}.zip because the
issue can be easily solved by copying the files from one location to the other.
My intention was to call your atention to this point so the configuration scripts
of future gcc releases can be adjusted accordingly.
Yes, I still use gcc on plain DOS every time I make a new port of some GNU
product. I have to test if it can be configured and compiled on plain DOS too.

Regards,
Juan M. Guerrero