Mail Archives: djgpp-workers/1998/02/24/13:15:02
Laszlo Molnar wrote :
>
> I just said that after I unzipped gcc280b.zip and typed
>
> gcc -march=pentium foo.c
>
> it failed, because gcc found the old cc1.exe in $DJDIR/bin first.
This is a common problem, when you install a new package without
deinstalling the old one. I will include this in the README.
Sine I don't have them in $DJDIR/bin but in $DJDIR/lib/gcc-lib/...
already for a long time, I haven't seen this problem until now.
> I think gcc should start the new cpp and cc1, so you could move them
> to bin/djgpp/2.80/ or you might change the directory order.
Yes, this might be possible, but I do not want to do so, because
I want to have now slowly a configuration of the directories like
it is common for the GNU packages. That means I would be glad if
we would have sometimes all the files in nearly exact the same
places like they will be installed with
make install
and in this case here the compilers (cc1, cc1plus, ...) are installed
in $prefix/lib/gcc-lib/$target/$version and the directory
$prefix/bin/$target is meant to hold the tool binaries like from
the binutils.
> ps: my djgpp.env contains the following lines in [gcc]:
>
> [gcc]
> COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin
> LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib
Yes I know about this, and this is probably the reason. When setting
the $COMPILER_PATH, gcc will search there first before in directory
where I placed the compilers.
> ps2: the last 2 pathnames look strange for me...
Why this?
Robert
--
******************************************************
* email: Robert Hoehne <robert DOT hoehne AT gmx DOT net> *
* Post: Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW: http://www.tu-chemnitz.de/~sho/rho *
******************************************************
- Raw text -