libtool/libltdl problem

libtool/libltdl problem

[Leandro Q. Galvez]

Hi,

    I am trying to compile opie-image from a newly fetched sources from openembedded. But I hit this stumbling block that prevented me to make any progress for the whole day. My openembedded environment already built the libtool 2.2.4-r16 based on the dependency requirements of the opie-image receipe. But when the build process reached pulseaudio 0.9.15-r8.4, the process stopped with an error about liltdl not being found. searched through the directory and I confirmed that all the install and devel files are in the staging/../user/lib folder. Searched through the net and all the hits point that libtool 2.2 is required for this pulseaudio version. But all the files are there. Can anybody help me through this?

exact message:
checking for lt_dladvise_init in -lltdl... no
configure: error: Unable to find libltdl
FATAL: oe_runconf failed


Thanks and best regards,
Andy
From utx@penguin.cz Fri Jul 31 13:31:46 2009
Received: from [84.21.108.25] (helo

libtool/libltdl problem

[Leandro Q. Galvez]

Hi,

    I am trying to compile opie-image from a newly fetched sources from 
openembedded. But I hit this stumbling block that prevented me to make any 
progress for the whole day. My openembedded environment already built the 
libtool 2.2.4-r16 based on the dependency requirements of the opie-image 
receipe. But when the build process reached pulseaudio 0.9.15-r8.4, the 
process stopped with an error about liltdl not being found. searched through 
the directory and I confirmed that all the install and devel files are in 
the staging/../user/lib folder. Searched through the net and all the hits 
point that libtool 2.2 is required for this pulseaudio version. But all the 
files are there. Can anybody help me through this?

exact message extracted from oe's tmp/log.do_configure:
checking for lt_dladvise_init in -lltdl... no
configure: error: Unable to find libltdl
FATAL: oe_runconf failed

exact message extracted from pulseaudio's config.log:
configure:12966: checking ltdl.h usability
configure:12983: ccache 
arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s -mthumb-interwork 
 -mno-thumb -std=gnu99 -c -isystem/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/include 
 -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 
 -Wall -W -Wextra -pipe -Wno-long-long -Winline -Wvla -Wno-overlength-strings 
 -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare  
-Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition 
 -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes 
 -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn 
 -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter 
 -ffast-math -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option -isystem/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/include 
conftest.c >&5
configure:12990: $? = 0
configure:13004: result: yes
configure:13008: checking ltdl.h presence
configure:13023: 
arm-angstrom-linux-gnueabi-gcc -E -isystem/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/include 
conftest.c
configure:13030: $? = 0
configure:13044: result: yes
configure:13077: checking for ltdl.h
configure:13084: result: yes
configure:13089: checking for lt_dladvise_init in -lltdl
configure:13124: ccache 
arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=arm926ej-s -mthumb-interwork 
 -mno-thumb -std=gnu99 -o 
conftest -isystem/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/include 
 -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 
 -Wall -W -Wextra -pipe -Wno-long-long -Winline -Wvla -Wno-overlength-strings 
 -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare  
-Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition 
 -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes 
 -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn 
 -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter 
 -ffast-math -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option -isystem/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/include 
 -L/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/lib -Wl,-rpath-link,/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/lib -Wl,-O1 -Wl,--hash-style=gnu conftest.c -lltdl >&5conftest.c:38: warning: function declaration isn't a prototype[-Wstrict-prototypes]conftest.c:41: warning: function declaration isn't a prototype[-Wstrict-prototypes]conftest.c: In function 'main':conftest.c:41: warning: old-style function definition[-Wold-style-definition]/media/OpieDrive/oebase/dragon/tmp/staging/armv5te-angstrom-linux-gnueabi/usr/lib/libltdl.so: undefined reference to `lt_libltdl_LTX_preloaded_symbols'collect2: ld returned 1 exit statusThanks and best regards,Andy

Re: libtool/libltdl problem

[Koen Kooi]

On 03-08-09 06:12, Leandro Q. Galvez wrote:
>
> Hi,
>
> I am trying to compile opie-image from a newly fetched sources from
> openembedded.

Please update, this was fixed for libtool 2.2.4 last week and for 2.2.6a 
yesterday.

regards,

Koen

Re: libtool/libltdl problem

[Leandro Q. Galvez]

Updating now... Can you tell me where the fix is? Just would like to know 
because it seems that this error is so common.

Thanks and best regards,
Andy

----- Original Message ----- 
From: "Koen Kooi" <k.kooi@student.utwente.nl>
To: <openembedded-devel@openembedded.org>
Sent: Monday, August 03, 2009 3:12 PM
Subject: Re: [oe] libtool/libltdl problem


> On 03-08-09 06:12, Leandro Q. Galvez wrote:
>>
>> Hi,
>>
>> I am trying to compile opie-image from a newly fetched sources from
>> openembedded.
>
> Please update, this was fixed for libtool 2.2.4 last week and for 2.2.6a 
> yesterday.
>
> regards,
>
> Koen
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

Re: libtool/libltdl problem

[Stanislav Brabec]

Leandro Q. Galvez wrote:
> Updating now... Can you tell me where the fix is? Just would like to know 
> because it seems that this error is so common.

It was my mistake in recipes/libtool/libtool*.bb:
ac_cv_path_... used a bash specific notation.
ac_cv_path_SED contained in typo.

It was broken by:
2e0fa4918d643ce6ec0299cd31cfe1c346e4bce3
My attempt to fix path to grep and sed (force paths from recipes instead
of checking grep and sed on host system) contained a bash specific
quotation and one ugly typo.

I hope that all these issues are fixed by:
1da1656c677dc3bf044f0e705ba6db8b5c825996
0131d2ec1d1e49a1facbc02234d5a70f8b67425e
f88d3e68e399069ba38f21cd4aa02b9dfcf487fc

These fixes should make libtool working again.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus

Re: libtool/libltdl problem

[Stanislav Brabec]

Stanislav Brabec wrote:

> I hope that all these issues are fixed by:

> These fixes should make libtool working again.

Well, yet another problem found:

libtool-cross and -sdk packages used target paths to grep and sed.
Target paths should be used only for libtool package and nothing else.
libtool-cross, libtool-native and libtool-sdk should use values provided
by system check. Fixed by:
daf5409a75e97aa5a60b11e9f150e2532676889e

If you know a better way, how to apply variables just for the target
build and not for -native, -cross and -sdk builds, feel free to improve
the recipe.

I found one possible consequent mis-compilation: imagemagick fixed by PR
bump: de1cf42779c207621d25afc08ad65f655494d573

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus

Re: libtool/libltdl problem

[Leandro Q. Galvez]

Thanks guys for the replies.

----- Original Message ----- 
From: "Stanislav Brabec" <utx@penguin.cz>
To: <openembedded-devel@lists.openembedded.org>
Sent: Monday, August 03, 2009 11:09 PM
Subject: Re: [oe] libtool/libltdl problem


> Stanislav Brabec wrote:
> 
>> I hope that all these issues are fixed by:
> 
>> These fixes should make libtool working again.
> 
> Well, yet another problem found:
> 
> libtool-cross and -sdk packages used target paths to grep and sed.
> Target paths should be used only for libtool package and nothing else.
> libtool-cross, libtool-native and libtool-sdk should use values provided
> by system check. Fixed by:
> daf5409a75e97aa5a60b11e9f150e2532676889e
> 
> If you know a better way, how to apply variables just for the target
> build and not for -native, -cross and -sdk builds, feel free to improve
> the recipe.
> 
> I found one possible consequent mis-compilation: imagemagick fixed by PR
> bump: de1cf42779c207621d25afc08ad65f655494d573
> 
> -- 
> Stanislav Brabec
> http://www.penguin.cz/~utx/zaurus
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>