From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joel Sherrill <joel@OARcorp.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: pre-egcs 1.1 status for *-rtems 
Date: Tue, 14 Jul 1998 11:29:00 -0000
Message-id: <Pine.BSF.3.96.980714112126.10553H-100000@vespucci.advicom.net>
References: <16184.900432489@hurl.cygnus.com>
X-SW-Source: 1998-07/msg00492.html

On Tue, 14 Jul 1998, Jeffrey A Law wrote:

>   In message < Pine.BSF.3.96.980714072626.27184B-100000@vespucci.advicom.net >you write:
>   > 
> ?!?  You sent me exactly what was needed the first time.  

<sigh>  I must need some time off. :)

> Just before the code which checks for assembler features.

> The problem appears to be that gcc/configure did not find the assembler
> sources and thus can't determine what assembler version you've got.  So
> we have to debug configure.  Too bad there's no such thing as a sgdb :-)

Did it and learned that you are right.  gcc/configure is not finding the
gas/configure.in because of the way it is following the symlinks.   I have
a tree symlinked like the one-tree script does.  Here is enough of the
link stuff to show what is happening.

      rm -rf src
      mkdir src
      cd src
      for f in gcc libio libstdc++ texinfo xiberty
      do
          ln -s ../${GCC}/${f} . 
      done
      for f in bfd binutils gas gprof ld opcodes etc
      do
           ln -s ../${BINUTILS}/$f .
      done
      ln -s ../${NEWLIB}/newlib .

So when you are in build/gcc:

$ ls -l ../../src/gcc
lrwxrwxrwx   1 joel     users          20 Jul 14 10:51 ../../src/gcc ->
../egcs-19980628/gcc
ls -l ../../src/gas
lrwxrwxrwx   1 joel     users          21 Jul 14 10:51 ../../src/gas ->
../binutils-2.9.1/gas

But ... somehow the symlinks do not get followed as one would like.
Watch this:

$ pwd
/usr1/rtems/work/tools/b/gcc
$ cd ../../src/gcc/../gas
$ pwd
/usr1/rtems/work/tools/src/gas
$ cd -
$ pwd
/usr1/rtems/work/tools/b/gcc
$ ls -l ../../src/gcc/../gas
ls: ../../src/gcc/../gas: No such file or directory

I am not a symlink expert but it looks like it is not being followed as
expected.

--joel