RE: Installation Problems

[David Korn <dkorn at pixelpower dot com>]

>-----Original Message-----
>From: Kai Ruottu [mailto:kai.ruottu@luukku.com]
>Sent: 18 January 2001 10:12

>David Korn wrote:
>> 
>>   Yep, it didn't find your target headers.  Contrary to what the docs
>> tend to say, you should put them in $prefix/$target/sys-include, rather
>> than $prefix/$target/include, or you can just tell the compiler where 
>> they are at configure time by adding the option 
>> --with-headers=/path/to/headers to your configure command.
>
> Sigh, I have tried to explain that the 'sys-include' is for the 3rd-party
>headers used with a cross-compiler (the 'SYSTEM_INCLUDE_DIR'), while the
>'include' is for the standard C headers (the 'STANDARD_INCLUDE_DIR').

    Kai, just a few points here...

  He *IS* building a cross compiler.  Now, I am under the impression that
fixincs needs to be run on the standard C headers for a target board, 
because they often aren't 100% ANSI compatible, or need to be modified to
reflect the different functionality that libgcc might provide compared to
the OS vendors libs.  So I have the idea that fixincs must be run on the
vendor headers a) in order to build libgcc correctly and b) in order to
have valid headers that will work with gcc after installation.

  I am also firmly convinced (because I've tried it over and over again)
that fixincs will never be run on the files in $prefix/$target/include, only
on the files in $prefix/$target/sys-include.

  Therefore, if the OS vendor headers are to be fixinc'd, they must be
in sys-include.  And if they aren't to be fixinc'd, why does fixincl.x
have OS vendor specific patches for systems such as VxWorks?

>The system-dependent headers, ie. specific for just the one PC, should be
>put into the 'sys-include'.

  I can't make sense of this, I'm afraid, "Specific for just the one PC",
to me means 'this one here on my desk but not that identical one on the
next desk'.  Unless these headers contain the hostname or other similar
unique identifier I can't imagine what headers might meet this standard ?

       DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com