This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Yes, you are hitting a common problem building cross-gcc, in that the gcc build wants to open and read several header files that are expected to exist for the target compile-and-link-time environment. It will use these header files to build library routines for the target compile-and-link-time environment. It is generally up to you to somehow get those header files in place. This can be easy or hard, depending on the target environment. This whole sub-topic is poorly documented, in the "outdated" faq you quoted, and even in the "better" faq that dkegel quoted. I'm hoping someone will elaborate in much greater detail on this topic, within the actual documentation, and not just repeated queries on the mailer list. (I'd volunteer, but I don't get the whole picture enough yet!) I'd like to see a list of all the header files that will be expected to exist, and what their content is expected to be, so that we may synthesize them from scratch if needed. There seems to be some partial solution you can use, by utilizing the --without-headers configure flag, but again, this is not sufficiently documented. Hope this helps! Rick ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |