All of lore.kernel.org
 help / color / mirror / Atom feed
* libtool issues with angstrom and classpath
@ 2008-07-06 15:06 Robert Schuster
  2008-07-06 16:04 ` Koen Kooi
  2008-07-11  8:58 ` Koen Kooi
  0 siblings, 2 replies; 4+ messages in thread
From: Robert Schuster @ 2008-07-06 15:06 UTC (permalink / raw)
  To: openembedded-devel

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

hi,
koen already told me that there will be libtool problems when building
classpath in angstrom 2008.1.

what I get are the following error messages:

i686-linux-libtool: link: unsupported hardcode properties
i686-linux-libtool: link: See the libtool documentation for more
information.
i686-linux-libtool: link: Fatal configuration error.

Caused by the following command:

make[3]: Entering directory
`/home/rob/oe/beagle/tmp/work/i686-linux/classpath-initial-0.93-r1/classpath-0.93/native/jni/java-net'
/bin/sh ../../../i686-linux-libtool --tag=CC   --mode=link ccache gcc -W
-Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes
-Wno-long-long -Wstrict-prototypes -pedantic -Werror
-isystem/home/rob/oe/beagle/tmp/staging/i686-linux/usr/include -Os
-module -version-info 0:0:0 -no-undefined
-L/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
-Wl,-rpath-link,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
-Wl,-rpath,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib -Wl,-O1 -o
libjavanet.la -rpath
/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib/classpath-initial
javanet.lo java_net_VMInetAddress.lo java_net_VMNetworkInterface.lo
java_net_VMURLConnection.lo gnu_java_net_VMPlainSocketImpl.lo
gnu_java_net_local_LocalSocketImpl.lo
../../../native/jni/classpath/jcl.lo
../../../native/jni/native-lib/libclasspathnative.la -lmagic

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?

Regards
Robert



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: libtool issues with angstrom and classpath
  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
  1 sibling, 0 replies; 4+ messages in thread
From: Koen Kooi @ 2008-07-06 16:04 UTC (permalink / raw)
  To: openembedded-devel

Robert Schuster wrote:
> hi,
> koen already told me that there will be libtool problems when building
> classpath in angstrom 2008.1.
>
> what I get are the following error messages:
>
> i686-linux-libtool: link: unsupported hardcode properties
> i686-linux-libtool: link: See the libtool documentation for more
> information.
> i686-linux-libtool: link: Fatal configuration error.
>
> Caused by the following command:
>
> make[3]: Entering directory
> `/home/rob/oe/beagle/tmp/work/i686-linux/classpath-initial-0.93-r1/classpath-0.93/native/jni/java-net'
> /bin/sh ../../../i686-linux-libtool --tag=CC   --mode=link ccache gcc -W
> -Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes
> -Wno-long-long -Wstrict-prototypes -pedantic -Werror
> -isystem/home/rob/oe/beagle/tmp/staging/i686-linux/usr/include -Os
> -module -version-info 0:0:0 -no-undefined
> -L/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath-link,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib -Wl,-O1 -o
> libjavanet.la -rpath
> /home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib/classpath-initial
> javanet.lo java_net_VMInetAddress.lo java_net_VMNetworkInterface.lo
> java_net_VMURLConnection.lo gnu_java_net_VMPlainSocketImpl.lo
> gnu_java_net_local_LocalSocketImpl.lo
> ../../../native/jni/classpath/jcl.lo
> ../../../native/jni/native-lib/libclasspathnative.la -lmagic
>
> 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?

I suspect that it doesn't like getting a lib directly (-lmagic), but 
want a .la file instead. I don't know a lot about libtool, so please 
speak up if this is nonsense :)

regards,

Koen




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: libtool issues with angstrom and classpath
  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
  1 sibling, 1 reply; 4+ messages in thread
From: Koen Kooi @ 2008-07-11  8:58 UTC (permalink / raw)
  To: openembedded-devel

Robert Schuster wrote:
> hi,
> koen already told me that there will be libtool problems when building
> classpath in angstrom 2008.1.
>
> what I get are the following error messages:
>
> i686-linux-libtool: link: unsupported hardcode properties
> i686-linux-libtool: link: See the libtool documentation for more
> information.
> i686-linux-libtool: link: Fatal configuration error.
>
> Caused by the following command:
>
> make[3]: Entering directory
> `/home/rob/oe/beagle/tmp/work/i686-linux/classpath-initial-0.93-r1/classpath-0.93/native/jni/java-net'
> /bin/sh ../../../i686-linux-libtool --tag=CC   --mode=link ccache gcc -W
> -Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes
> -Wno-long-long -Wstrict-prototypes -pedantic -Werror
> -isystem/home/rob/oe/beagle/tmp/staging/i686-linux/usr/include -Os
> -module -version-info 0:0:0 -no-undefined
> -L/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath-link,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib -Wl,-O1 -o
> libjavanet.la -rpath
> /home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib/classpath-initial
> javanet.lo java_net_VMInetAddress.lo java_net_VMNetworkInterface.lo
> java_net_VMURLConnection.lo gnu_java_net_VMPlainSocketImpl.lo
> gnu_java_net_local_LocalSocketImpl.lo
> ../../../native/jni/classpath/jcl.lo
> ../../../native/jni/native-lib/libclasspathnative.la -lmagic
>
> 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)

regards,

Koen



>
> Regards
> Robert
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel





^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: libtool issues with angstrom and classpath
  2008-07-11  8:58 ` Koen Kooi
@ 2008-07-12 18:01   ` Robert Schuster
  0 siblings, 0 replies; 4+ messages in thread
From: Robert Schuster @ 2008-07-12 18:01 UTC (permalink / raw)
  To: openembedded-devel; +Cc: Koen Kooi

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-07-12 18:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.