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] |
On Wed, 5 Mar 1997, Bernie Doehner wrote: > > Hi Pedro: > > Sorry to hear about your still having trouble even with gmake. What do > you mean with "replace libgcc1.a for sco"? > The cross-patch provides code that replaces some math stuff. This makes it possible to provide a null libgcc.a. This code isn't available for SCO, so I'm getting a libgcc1.a generated on an SCO box (GNU's info file has information on this). > At least under BSD, you don't > touch the BSD libgcc1.a. In the process of building the toolchain, you > compile a new libgcc.a that will be used with your crosscompiler (ONLY). > This is only valid for some hosts. > You are the first person I read about that will be trying 2.7.2.1 and > 2.7.2.2. I think the changes are rather minor, but I don't know. I assume > you are applying the following patches to 2.7.2: > crossgcc 2.7.2-2.7.2.1 2.7.2.1-2.7.2.2 > I'm following this order: 1) get from the FSF gcc-2.7.2.1.tar.gz, untar, etc 2) Apply the crossgcc patch You shouldn't have problems with this, and it seems to build fine (isn't finished yet). 3) If you want adventure you can apply 2.7.2.1-2.7.2.2.diff : If you are lucky, you will get only one reject (in the top Makefile). Look at *.rej and apply the diff by hand. Now you're on your own. > > Also: Not that it matters and awful lot, but what is your target? > For sco.. i386-sco, but I'm also building i386-linux and i386-go32 Pedro. > Bernie > >