This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Doug Evans wrote: > > Date: Wed, 5 Mar 1997 13:28:08 -0500 (EST) > From: Bernie Doehner <bad@uhf.wireless.net> > > > Are you building in the source tree or in a separate directory? > > > > Secondly, newlib should be buildable by non GNU makes, > > though one is required to build in the source tree if one > > is not using GNU make. > > Sorry to disagree, but building in a SEPARATE directory with FreeBSD make > does not work. I'll try it again before writing up the patch. > > I'm trying to make sure we're on the same wavelength here. > > If one builds in a separate directory (i.e. srcdir != .) > then one is required to use GNU make. I'll reword the > FAQ to state this unequivocally (right now the FAQ says > if one is using a make that understands VPATH one can build > with srcdir != . --- SunOS make pretends to understand VPATH, but > not to the extent that makes it usable without an unacceptable effort, IMHO). Sorry to disagree, but building in the same source tree also required GNU make! Let me point out this is really a NEWLIB problem: I reported this some days ago in newlib@cygnus.com but forgot it the moment of building the crosscompiler (where this discussion started). FreeBSD also has available GNU make so I see this discusion is not leading too far. We should center on how upgrading the tools could affect the patches and procedures for building the cross compiler. For example: What happened with new GO32 and the WINNT support? What information do I need to replace the libgcc1.a in 386 boxes? BTW, there is a small bug in binutils-2.7 (under BSD boxes) that will be fixed shortly :(. Pedro.