[Fwd: newlib-1.8.2 problem]

[Kai Ruottu <karuottu at freenet dot hut dot fi>]

Somehow I managed to reply to only myself and Linux-Netscape didn't let edit anything
in the 'Unsent' folder...

---

• To: Kai Ruottu <karuottu at freenet dot hut dot fi>
• Subject: Re: newlib-1.8.2 problem
• From: Kai Ruottu <karuottu at freenet dot hut dot fi>
• Date: Tue, 19 Sep 2000 14:11:30 +0300
• Organization: Freenet Finland
• References: <MIEMKFFHIDIPDFPKBGPGAEHECHAA.ken@sdt.be> <39C72454.D8326020@freenet.hut.fi>

Kai Ruottu wrote:
> 
> -------------------------- clip -------------------------------------------
>         echo $$r/gcc/xgcc -B$$r/gcc/ -B$(build_tooldir)/bin/ \
> -idirafter $$r/$(TARGET_SUBDIR)/newlib/targ-include \
> -idirafter $$r/newlib/libc/include -nostdinc; \
>       fi; \
>     else \
>       echo $$r/gcc/xgcc -B$$r/gcc/ -B$(build_tooldir)/bin/ -I$(build_tooldir)/include; \
> -------------------------- clip -------------------------------------------

 The '-B$(build_tooldir)/lib/' or '-L$(build_tooldir)/lib' addition may also be necessary.
While building the following things must be found for the no-newlib case:

  1. The target binutils, the original ' -B$(build_tooldir)/bin/' takes care of this

  2. The target libs, the '-L$(build_tooldir)/lib' would take care of this.

  3. The target headers, the '-I$(build_tooldir)/include' would take care of this.

 What to add to the 'newlib' (and the 'winsup') case, will be left as homework...;-)

Cheers, Kai

---

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