Mail Archives: djgpp/1998/01/03/18:46:53
Roger wrote :
>
> Please, please, please, try to think back to when you were new to something (as
> I am to things GNUish). There is so much to read and learn. I have never used
> Unix, configure scripts, etc.
But anyone has the freedom to start with it :-)
> But there is the small problem (actually a big problem to me) of how the
> hard-wired path got into the executable. It isn't in the source, as far as I can
> see. Presumably if I follow the instructions a different path will be hard-wired
> in, albeit one that is on my computer.
The path which you mean, is "hard-wired" in ld.exe when the object file
ldmain.c is compiled. (in the ld subdirectory) When compiling it gets
via
commandline from the makefile a define like
-DSCRIPTDIR='"$(scriptdir)"'
where the variable scriptdir is set by the main configure script which
is based
on the $(prefix) variable. And as I built binutils on my computer with
configure --prefix=${DJDIR}
this was then fault. If you dont give explicit the --prefix option to
the
configure script, the default prefix (/usr/local) is used (like I made
it
for the newly built binutils, which I have uploaded).
> Perhaps you would be kind enough to provide a pointer as to where/how it got in.
> I guess it's something to do with the configure script.
Exact, see above.
BTW: If you really want to start and learn about porting or compiling
GNU packages for your own, I would really not recommend the binutils
package, since it is very complex and as you saw it already it needs
a lot of other utils installed (this saved me a lot of work when doing
the DJGPP port :-) ).
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 -