From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: libtool issues with angstrom and classpath
Date: Sat, 12 Jul 2008 20:01:48 +0200 [thread overview]
Message-ID: <4878F18C.2080404@gmx.net> (raw)
In-Reply-To: <g577ce$6hu$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
Hi Koen,
Koen Kooi schrieb:
>>
>> I debugged this problem to the point where I found out that it does not
>> like the '-lmagic'. If I remove that from the makefile the build
>> continues. However this cannot be the real fix.
>>
>> What is wrong here and how should I fix it?
>>
>> What other program that uses libtool and links to an external library
>> can I look at and study their autotools files?
>
> It seems that the following bit causes the error:
>
> ./configure.ac:383: AC_CHECK_LIB(magic, magic_open, LIBMAGIC=-lmagic)
Thanks for looking at this. I found a different 'solution'. In the
current libtool scripts that are generated from ./configure the variable
hardcode_direct is empty. For earlier libtool versions this was set to
'no'. If I manually edit the script and set the variable to 'no' the
build continues just fine.
I am currently discussing this on the libtool mailing list. If you know
other packages that break with the 'invalid hardcode properties' error
message you may try the above workaround.
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2008-07-12 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 15:06 libtool issues with angstrom and classpath Robert Schuster
2008-07-06 16:04 ` Koen Kooi
2008-07-11 8:58 ` Koen Kooi
2008-07-12 18:01 ` Robert Schuster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4878F18C.2080404@gmx.net \
--to=thebohemian@gmx.net \
--cc=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.