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] |
On Thu, Jul 04, 2002 at 11:58:49AM +0100, Yves Rutschle wrote: > On Wed, Jul 03, 2002 at 10:07:20AM -0700, Aaron J. Grier wrote: > > I do not know why configure does not generate proper include > > pathnames, but I have used the symlink trick as a workaround. > > Because somebody might want to build gcc targeting another library > than newlib. Glibc comes to mind for example. but in this case (and mine as well) --with-newlib was specified. > Therefore it would be questionnable to tie gcc to a particular C > library. It is part of the normal build process to provide gcc with > the target library and header files. agreed. but since --with-newlib was specified, shouldn't the autotools be smart enough to put the proper system include paths? -- Aaron J. Grier | Frye Electronics, Tigard, OR | aaron@frye.com ------ 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] |