PREFIX changed?

[Dan Kegel]

Steven Scholz wrote:
> is there any special reason why PREFIX was changed from
>     
>     PREFIX=${PREFIX-$RESULT_TOP/$TARGET/$TOOLCOMBO}
> to
>     PREFIX=${PREFIX-$RESULT_TOP/$TOOLCOMBO/$TARGET}

Yes.  Here's what I wrote earlier:
http://sources.redhat.com/ml/crossgcc/2005-05/msg00078.html

>> While polishing up the rpm support in
>> preparation for getting it into Fedora Extras,
>> I realized that
>> /opt/crosstool/i686-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2
>> /opt/crosstool/i686-unknown-linux-gnu/gcc-2.95.3-glibc-2.3.5
>> /opt/crosstool/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.2.2
>> /opt/crosstool/arm-unknown-linux-gnu/gcc-2.95.3-glibc-2.3.5
>> is backwards because it interleaves the results from building
>> two toolchains for different targets.  So I'm flipping the last
>> two parts of the path, e.g.
>> /opt/crosstool/gcc-2.95.3-glibc-2.2.2/i686-unknown-linux-gnu
>> /opt/crosstool/gcc-2.95.3-glibc-2.2.2/arm-unknown-linux-gnu
>> /opt/crosstool/gcc-2.95.3-glibc-2.3.5/i686-unknown-linux-gnu
>> /opt/crosstool/gcc-2.95.3-glibc-2.3.5/arm-unknown-linux-gnu
>> That way the output from a given pair of gcc and glibc tarballs
>> is all gathered under a single directory.


> Is it enough if I change that line in all.sh if I don't like it? Or are 
> there more places to edit?

That's the place.
- Dan


-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

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