970901 - cross problem with libio/gen-params

970901 - cross problem with libio/gen-params

[Joel Sherrill]

I tried to build egcs-970901 to target sparc-rtems.  This was a buidl from
scratch and I did not have another sparc-rtems toolset in my path. The
script libio/gen-params wanted to use an installed sparc-rtems-nm not the
one which is still in the build tree.  It does not look like gen-params
has changed since the 970825 snapshot, so I do not know what broke.

I have pasted the error message hoping someone recognizes the problem

rootme=`pwd`/ ; export rootme; \
CC="/usr1/rtems/work/tools/build-sparc-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-sparc-tools/gcc/ -idirafter
/usr1/rtems/work/tools/build-sparc-tools/sparc-rtems/newlib/targ-include
-idirafter /usr1/rtems/work/tools/src/newlib/libc/include -nostdinc";
export CC; \
CXX="/usr1/rtems/work/tools/build-sparc-tools/gcc/xgcc
-B/usr1/rtems/work/tools/build-sparc-tools/gcc/ -idirafter
/usr1/rtems/work/tools/build-sparc-tools/sparc-rtems/newlib/targ-include
-idirafter /usr1/rtems/work/tools/src/newlib/libc/include -nostdinc
-nostdinc++ -g -O2"; export CXX; \
CONFIG_NM="sparc-rtems-nm"; export CONFIG_NM; \
/bin/sh ../../../src/libio/gen-params LIB_VERSION=2.8.0  >tmp-params.h
../../../src/libio/gen-params: sparc-rtems-nm: command not found
../../../src/libio/gen-params: sparc-rtems-nm: command not found
sparc-rtems-nm failed to find FUNC in dummy.o!
gmake[1]: *** [_G_config.h] Error 255
gmake[1]: Leaving directory
`/usr1/rtems/work/tools/build-sparc-tools/sparc-rtems/libio'
gmake: *** [all-target-libio] Error 2

Thanks.


--joel
Joel Sherrill                    Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (205) 722-9985

Re: 970901 - cross problem with libio/gen-params

[Ian Lance Taylor]

   Date: Wed, 3 Sep 1997 12:08:21 -0500 (CDT)
   From: Joel Sherrill <joel@OARcorp.com>

   I tried to build egcs-970901 to target sparc-rtems.  This was a buidl from
   scratch and I did not have another sparc-rtems toolset in my path. The
   script libio/gen-params wanted to use an installed sparc-rtems-nm not the
   one which is still in the build tree.  It does not look like gen-params
   has changed since the 970825 snapshot, so I do not know what broke.

I don't know if this is the problem, but here is a potential problem
which might cause the symptoms you are reporting.

The current development sources of the binutils generate nm-new rather
than nm.new.  This is for easier use on Windows systems, so that we
can generate nm-new.exe without worrying about the multiple extensions
in nm.new.exe (it's true that nm.new.exe will work on new MS file
systems, but it's easier to sidestep the whole issue for the benefit
of old 8.3 file systems).

The top level Makefile.in in the egcs release looks for nm-new.  If
you are using this with, e.g., binutils 2.8.1, which produces nm.new,
then the top level Makefile.in won't find the nm program in the build
directory.  That will cause it to use nm from your path instead.

The fix is to change the top level Makefile.in to look for nm.new
rather than nm-new.  Similar cases arise for some other programs;
search for `-new' in Makefile.in.

I don't know if this is really an egcs problem; the problem will only
arise if you try to mix egcs with the binutils 2.8.1 release in the
same directory tree.

When the egcs CVS server is up and running, I hope to start putting
the development binutils releases on it as well.  At that time, it
will be possible to get a single consistent tree.

Ian

Re: 970901 - cross problem with libio/gen-params

[Joel Sherrill]

On Wed, 3 Sep 1997, Ian Lance Taylor wrote:

> I don't know if this is the problem, but here is a potential problem
> which might cause the symptoms you are reporting.

Sounds like this is the culprit.  I am trying your suggestion now.

> The current development sources of the binutils generate nm-new rather
> than nm.new.  This is for easier use on Windows systems, so that we
> can generate nm-new.exe without worrying about the multiple extensions
> in nm.new.exe (it's true that nm.new.exe will work on new MS file
> systems, but it's easier to sidestep the whole issue for the benefit
> of old 8.3 file systems).

Unfortunately binutils 2.8.1 actually builds nm.new ld.new and strip.new.
:(  

> The top level Makefile.in in the egcs release looks for nm-new.  If
> you are using this with, e.g., binutils 2.8.1, which produces nm.new,
> then the top level Makefile.in won't find the nm program in the build
> directory.  That will cause it to use nm from your path instead.

It looks like this is enought o get the build past this point.

> I don't know if this is really an egcs problem; the problem will only
> arise if you try to mix egcs with the binutils 2.8.1 release in the
> same directory tree.

This was the first egcs snapshot I could not build one-tree style with
egcs.

> When the egcs CVS server is up and running, I hope to start putting
> the development binutils releases on it as well.  At that time, it
> will be possible to get a single consistent tree.

Does this mean that we will eventually be looking at egcs being a full
toolset tree?

--joel

Re: 970901 - cross problem with libio/gen-params

[Ian Lance Taylor]

   Date: Wed, 3 Sep 1997 12:30:48 -0500 (CDT)
   From: Joel Sherrill <joel@OARcorp.com>

   > When the egcs CVS server is up and running, I hope to start putting
   > the development binutils releases on it as well.  At that time, it
   > will be possible to get a single consistent tree.

   Does this mean that we will eventually be looking at egcs being a full
   toolset tree?

Well, I hope that it means we will eventually be looking at the CVS
server being able to provide a full toolset tree.  I doubt the whole
thing will ever be wrapped up into a single snapshot--it would be
rather large.

Ian

Re: 970901 - cross problem with libio/gen-params

[Joel Sherrill]

On Wed, 3 Sep 1997, Ian Lance Taylor wrote:

>    Does this mean that we will eventually be looking at egcs being a full
>    toolset tree?
> 
> Well, I hope that it means we will eventually be looking at the CVS
> server being able to provide a full toolset tree.  I doubt the whole
> thing will ever be wrapped up into a single snapshot--it would be
> rather large.

I can vouch for that.  The last tree I bundled up included binutils,
gcc, newlib, and gnat.  It weighed in at a hefty 20.7 Mbytes of soruce. :)

--joel

Re: 970901 - cross problem with libio/gen-params

[David Bristow]

> 
> I can vouch for that.  The last tree I bundled up included binutils,
> gcc, newlib, and gnat.  It weighed in at a hefty 20.7 Mbytes of soruce. :)
> 
> --joel
> 

20.7 Mbytes of COMPRESSED source, I think

David Bristow
dbristow@lynx.dac.neu.edu

Re: 970901 - cross problem with libio/gen-params

[Joel Sherrill]

On Wed, 3 Sep 1997, David Bristow wrote:

> > 
> > I can vouch for that.  The last tree I bundled up included binutils,
> > gcc, newlib, and gnat.  It weighed in at a hefty 20.7 Mbytes of soruce. :)
> > 
> > --joel
> > 
> 
> 20.7 Mbytes of COMPRESSED source, I think

Keep me honest. :)  Yes it was compressed.  

--joel