This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: "empty" Makefile
- From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
- To: Ethan Tira-Thompson <ejt at andrew dot cmu dot edu>
- Cc: newlib at sources dot redhat dot com
- Date: Sun, 11 Sep 2005 10:06:12 +0200
- Subject: Re: "empty" Makefile
- References: <5BC0210F-B377-43BC-BB4B-22AA33813B0F@andrew.cmu.edu>
On Sun, 2005-09-11 at 03:50 -0400, Ethan Tira-Thompson wrote:
> And now for my own question...
> I'm trying to build a cross compiler from powerpc (host) to mips
> (target). Here's the script I'm running (PREFIX is set to /usr/local/
> OPEN_R_SDK_new, TARGET is mipsel-linux):
> ...and it will generator a no-op Makefile which has all empty targets.
> This seems to be because of line 1508 of configure:
> 1507: mips*-*-linux*)
> 1508: noconfigdirs="$noconfigdirs target-newlib target-libgloss"
> 1509: ;;
> If I comment out 1508, then the build can proceed as expected.
>
> My question is, why is the package disabled for all of the mips
> targets?
It isn't.
newlib is disabled for mips*-*-linux*, but it isn't disabled for other
mips*-* targets (eg. mips-rtems, mips-elf etc.)
Probably, mips*-*-linux* uses glibc2 and doesn't use newlib.
> Does the current newlib release not support mips, or is
> this some kind of oversight?
It does support the mips architecture for a variety of OSes,
but it doesn't support "Linux on mips".
> @@ -1505,7 +1505,7 @@
> noconfigdirs="$noconfigdirs target-newlib ${libgcj}"
> ;;
> mips*-*-linux*)
> - noconfigdirs="$noconfigdirs target-newlib target-libgloss"
> +# noconfigdirs="$noconfigdirs target-newlib target-libgloss"
> ;;
> mips*-*-*)
> noconfigdirs="$noconfigdirs gprof ${libgcj}"
Have a look at the snippet above: It means, mips*-*-linux* is not
supported by newlib.
Ralf