This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

PATH in Dan Kegel's script crosstool.sh

From: Michael LeBlanc <leblanc at skycomputers dot com>
To: crossgcc at sources dot redhat dot com
Date: Wed, 24 Sep 2003 11:31:10 -0400
Subject: PATH in Dan Kegel's script crosstool.sh
Reply-to: mike at whitehillfarm dot com

In Dan's crosstool.sh there is

   69  # make sure the build product's binaries are in the search path
   70  PATH="${PREFIX}/bin:${PATH}"
   71  export PATH

When I run it, PREFIX becomes, for example, the following:

/somewhere/result/powerpc-mike-linux-gnualtivec/gcc-3.3-glibc-2.3.2

In bin/ under there, I find powerpc-mike-linux-gnualtivec-gcc and all
the other executables with names powerpc-mike-linux-gnualtivec-*.
Are they used by those names in the scripts and Makefiles?

Shouldn't line 70 read like this?

PATH="${PREFIX}/${TARGET}/bin:${PATH}"

Now "gcc" will resolve to the build's gcc.

Mike


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

Follow-Ups:
- Re: PATH in Dan Kegel's script crosstool.sh
  - From: Dan Kegel

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]