Re: makefile with "ln"
- From: "John Small" <jsmall@xxxxxxxxxxxx>
- Date: Mon, 02 Feb 2009 13:04:20 -0600
On Mon, 2 Feb 2009 04:50:12 UTC, KO Myung-Hun <komh@xxxxxxxxxxxx>
wrote:
Hi/2.
John Small wrote:
ar.exe cru .libs/boinc_api.a boinc_api.o reduce_main.o
graphics2_util.o
echo .libs/boinc_api.a
.libs/boinc_api.a
creating libboinc_api.la
(cd .libs && rm -f libboinc_api.la && ln -s ../libboinc_api.la
libboinc_api.la)
rm -f libboinc_api.a
ln .libs/libboinc_api.a
ln: accessing `.libs/libboinc_api.a': No such file or directory
make: *** [libboinc_api.a] Error 1
I looked at api/Makefile.am.
-----
libboinc_api.a: libboinc_api.la
rm -f libboinc_api.a
ln .libs/libboinc_api.a
libboinc_graphics2.a: libboinc_graphics2.la
rm -f libboinc_graphics2.a
ln .libs/libboinc_graphics2.a
-----
Your logs say that boinc_api.a in .libs created successfully. But build
system of BOINC assume that the name of the created library has a 'lib'
prefix. It's not true for libtool for OS/2.
And 'ln TARGET' form is not supported on OS/2, I know. From help
message, it means 'create a link to TARGET in the current directory'. If
trying that, it reports 'Function not implemented'. I'm using 'ln (GNU
coreutils) 5.94'.
You should replace that ln parts with 'cp .libs/boinc_api.a
libboinc_api.a'. So does boinc_graphics2.a.
This is a build system bug of BOINC due to incompleted transition to
libtool as David said.
Finally, you should use coreutils supporting symbolic link, i.e.,
compiled by kLIBC to get the correct result.
By this, do you mean:
<ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd3.zip>?
If yes,
1) I have been using Paul Smedley's build environment. Is it OK to
unzip this file over this Paul's environment? Would doing so break or
fundamentally alter Paul's environment?
2) Do I then start using the usr/bin/gccenv.cmd contained in
<ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd3.zip> instead of Paul's
gcc335.cmd?
3) In the usr/doc/gcc-3.3.5/install.os2 file within
<ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd3.zip> it says: "If you
wanna use -Zomf you should check the usage output from emxomfld
carefully, cause additional environment setup might be required."
Could someone expand on this? What should I look for? What envrionment
settings might need adjustment?
Thanks for your help!
--
John Small
.
- Follow-Ups:
- Re: makefile with "ln"
- From: John Small
- Re: makefile with "ln"
- From: Dave Yeo
- Re: makefile with "ln"
- References:
- Re: makefile with "ln"
- From: KO Myung-Hun
- Re: makefile with "ln"
- Prev by Date: Re: makefile with "ln"
- Next by Date: Re: makefile with "ln"
- Previous by thread: Re: makefile with "ln"
- Next by thread: Re: makefile with "ln"
- Index(es):
Relevant Pages
|