public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
@ 2011-01-03 10:19 Kfir Lavi
  2011-01-03 18:41 ` Mike Frysinger
  0 siblings, 1 reply; 6+ messages in thread
From: Kfir Lavi @ 2011-01-03 10:19 UTC (permalink / raw
  To: gentoo-embedded

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

Hi,
when I try to cross compile sys-fs/e2fsprogs I get this error:
checking for blkid_get_cache in -lblkid... no

copying the uuid and blkid files to the cross environment solve the problem
and the package compiles.
cp /tmp/target_root/usr/lib/libuuid.* /usr/i686-gentoo-linux-gnu/usr/lib/
cp /tmp/target_root/usr/lib/libblkid.* /usr/i686-gentoo-linux-gnu/usr/lib/
cp /tmp/target_root/lib/libuuid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
cp /tmp/target_root/lib/libblkid.so.1*  /usr/i686-gentoo-linux-gnu/lib/

How can this problem be solved permanently?

Regards,
Kfir

[-- Attachment #2: Type: text/html, Size: 643 bytes --]

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

* Re: [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
  2011-01-03 10:19 [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no Kfir Lavi
@ 2011-01-03 18:41 ` Mike Frysinger
  2011-01-04  9:02   ` Patrice Tisserand
  0 siblings, 1 reply; 6+ messages in thread
From: Mike Frysinger @ 2011-01-03 18:41 UTC (permalink / raw
  To: gentoo-embedded; +Cc: Kfir Lavi

[-- Attachment #1: Type: Text/Plain, Size: 774 bytes --]

On Monday, January 03, 2011 05:19:58 Kfir Lavi wrote:
> when I try to cross compile sys-fs/e2fsprogs I get this error:
> checking for blkid_get_cache in -lblkid... no
> 
> copying the uuid and blkid files to the cross environment solve the problem
> and the package compiles.
> cp /tmp/target_root/usr/lib/libuuid.* /usr/i686-gentoo-linux-gnu/usr/lib/
> cp /tmp/target_root/usr/lib/libblkid.* /usr/i686-gentoo-linux-gnu/usr/lib/
> cp /tmp/target_root/lib/libuuid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
> cp /tmp/target_root/lib/libblkid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
> 
> How can this problem be solved permanently?

you should be emerging library packages into your SYSROOT (/usr/$CTARGET) 
before building/installing packages into your ROOT
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

* Re: [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
  2011-01-03 18:41 ` Mike Frysinger
@ 2011-01-04  9:02   ` Patrice Tisserand
  2011-01-04 18:59     ` Mike Frysinger
  0 siblings, 1 reply; 6+ messages in thread
From: Patrice Tisserand @ 2011-01-04  9:02 UTC (permalink / raw
  To: gentoo-embedded; +Cc: Kfir Lavi

Mike Frysinger wrote:
> On Monday, January 03, 2011 05:19:58 Kfir Lavi wrote:
>> when I try to cross compile sys-fs/e2fsprogs I get this error:
>> checking for blkid_get_cache in -lblkid... no
>>
>> copying the uuid and blkid files to the cross environment solve the problem
>> and the package compiles.
>> cp /tmp/target_root/usr/lib/libuuid.* /usr/i686-gentoo-linux-gnu/usr/lib/
>> cp /tmp/target_root/usr/lib/libblkid.* /usr/i686-gentoo-linux-gnu/usr/lib/
>> cp /tmp/target_root/lib/libuuid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
>> cp /tmp/target_root/lib/libblkid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
>>
>> How can this problem be solved permanently?
> 
> you should be emerging library packages into your SYSROOT (/usr/$CTARGET) 
> before building/installing packages into your ROOT
> -mike

Does adding -L /tmp/target_root/lib -L /tmp/target_root/usr/lib
-Wl,-rpath-link,/tmp/target_root/lib
-Wl,-rpath-link,/tmp/target_root/usr/lib to LDFLAGS could not be an
alternative ?

Patrice

----
This message contains confidential information and may contain information that is legally privileged.  If you have received this message by mistake, please immediately notify us and delete the original message. Thank you.  

Ce message contient des informations confidentielles.  S'il vous est parvenu par erreur, merci de bien vouloir nous en aviser par retour, de n'en faire aucun usage et de n'en garder aucune copie.
----



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

* Re: [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
  2011-01-04  9:02   ` Patrice Tisserand
@ 2011-01-04 18:59     ` Mike Frysinger
  2011-01-04 22:12       ` Patrice Tisserand
  0 siblings, 1 reply; 6+ messages in thread
From: Mike Frysinger @ 2011-01-04 18:59 UTC (permalink / raw
  To: gentoo-embedded; +Cc: Patrice Tisserand, Kfir Lavi

[-- Attachment #1: Type: Text/Plain, Size: 1149 bytes --]

On Tuesday, January 04, 2011 04:02:59 Patrice Tisserand wrote:
> Mike Frysinger wrote:
> > On Monday, January 03, 2011 05:19:58 Kfir Lavi wrote:
> >> when I try to cross compile sys-fs/e2fsprogs I get this error:
> >> checking for blkid_get_cache in -lblkid... no
> >> 
> >> copying the uuid and blkid files to the cross environment solve the
> >> problem and the package compiles.
> >> cp /tmp/target_root/usr/lib/libuuid.*
> >> /usr/i686-gentoo-linux-gnu/usr/lib/ cp
> >> /tmp/target_root/usr/lib/libblkid.* /usr/i686-gentoo-linux-gnu/usr/lib/
> >> cp /tmp/target_root/lib/libuuid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
> >> cp /tmp/target_root/lib/libblkid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
> >> 
> >> How can this problem be solved permanently?
> > 
> > you should be emerging library packages into your SYSROOT (/usr/$CTARGET)
> > before building/installing packages into your ROOT
> 
> Does adding -L /tmp/target_root/lib -L /tmp/target_root/usr/lib
> -Wl,-rpath-link,/tmp/target_root/lib
> -Wl,-rpath-link,/tmp/target_root/usr/lib to LDFLAGS could not be an
> alternative ?

no.  that's broken by design.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

* Re: [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
  2011-01-04 18:59     ` Mike Frysinger
@ 2011-01-04 22:12       ` Patrice Tisserand
  2011-01-05  7:03         ` Mike Frysinger
  0 siblings, 1 reply; 6+ messages in thread
From: Patrice Tisserand @ 2011-01-04 22:12 UTC (permalink / raw
  To: gentoo-embedded; +Cc: Kfir Lavi

On 01/04/2011 07:59 PM, Mike Frysinger wrote:
> On Tuesday, January 04, 2011 04:02:59 Patrice Tisserand wrote:
>> Mike Frysinger wrote:
>>> On Monday, January 03, 2011 05:19:58 Kfir Lavi wrote:
>>>> when I try to cross compile sys-fs/e2fsprogs I get this error:
>>>> checking for blkid_get_cache in -lblkid... no
>>>>
>>>> copying the uuid and blkid files to the cross environment solve the
>>>> problem and the package compiles.
>>>> cp /tmp/target_root/usr/lib/libuuid.*
>>>> /usr/i686-gentoo-linux-gnu/usr/lib/ cp
>>>> /tmp/target_root/usr/lib/libblkid.* /usr/i686-gentoo-linux-gnu/usr/lib/
>>>> cp /tmp/target_root/lib/libuuid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
>>>> cp /tmp/target_root/lib/libblkid.so.1*  /usr/i686-gentoo-linux-gnu/lib/
>>>>
>>>> How can this problem be solved permanently?
>>>
>>> you should be emerging library packages into your SYSROOT (/usr/$CTARGET)
>>> before building/installing packages into your ROOT
>>
>> Does adding -L /tmp/target_root/lib -L /tmp/target_root/usr/lib
>> -Wl,-rpath-link,/tmp/target_root/lib
>> -Wl,-rpath-link,/tmp/target_root/usr/lib to LDFLAGS could not be an
>> alternative ?
>
> no.  that's broken by design.
Thanks for your answer, I have found the following sentence in gentoo 
embedded handbook:
"""The common convention is to use your /usr/CTARGET/ tree as your 
sysroot as the include/library directories in this tree are already 
encoded into the gcc cross-compiler for searching. You could use another 
directory and then add custom -I/-L paths to your CPPFLAGS/LDFLAGS, but 
this has historically proven to be problematic. Yes, it works most of 
the time, but the corner cases are why this method is discouraged. In 
the embedded handbook, we'll assume you're using the sysroot as your 
development ROOT.
"""
Do you know where I can find references about these corner cases ?

Also how can I handle creating 2 different target rootfs with different 
libraries versions but using the same cross-compilation toolchain?
Do I need to duplicate environment or is there some tips ?

Regards,
Patrice





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

* Re: [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no
  2011-01-04 22:12       ` Patrice Tisserand
@ 2011-01-05  7:03         ` Mike Frysinger
  0 siblings, 0 replies; 6+ messages in thread
From: Mike Frysinger @ 2011-01-05  7:03 UTC (permalink / raw
  To: gentoo-embedded; +Cc: Patrice Tisserand, Kfir Lavi

[-- Attachment #1: Type: Text/Plain, Size: 1931 bytes --]

On Tuesday, January 04, 2011 17:12:58 Patrice Tisserand wrote:
> On 01/04/2011 07:59 PM, Mike Frysinger wrote:
> > On Tuesday, January 04, 2011 04:02:59 Patrice Tisserand wrote:
> >> Does adding -L /tmp/target_root/lib -L /tmp/target_root/usr/lib
> >> -Wl,-rpath-link,/tmp/target_root/lib
> >> -Wl,-rpath-link,/tmp/target_root/usr/lib to LDFLAGS could not be an
> >> alternative ?
> > 
> > no.  that's broken by design.
> 
> Thanks for your answer, I have found the following sentence in gentoo
> embedded handbook:
> """The common convention is to use your /usr/CTARGET/ tree as your
> sysroot as the include/library directories in this tree are already
> encoded into the gcc cross-compiler for searching. You could use another
> directory and then add custom -I/-L paths to your CPPFLAGS/LDFLAGS, but
> this has historically proven to be problematic. Yes, it works most of
> the time, but the corner cases are why this method is discouraged. In
> the embedded handbook, we'll assume you're using the sysroot as your
> development ROOT.
> """
> Do you know where I can find references about these corner cases ?

perhaps ive cited examples on this list in the past, but i dont recall.  i'll 
just refer to Bug 347489 and mention the same issue with like 
curses/bash/screen off the top of my head.

> Also how can I handle creating 2 different target rootfs with different
> libraries versions but using the same cross-compilation toolchain?
> Do I need to duplicate environment or is there some tips ?

i dont know why you'd do this, but the cleanest approach today would be to 
create a new cross-compiler toolchain with a slightly different vendor so you 
get unique paths.  i imagine it'd be possible to also take the default gcc 
specs, tweak the sysroot arg in it, and export the GCC_SPECS env var, but it 
could get messy as you'd have to remember what you have your env set to.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

end of thread, other threads:[~2011-01-05  7:14 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-03 10:19 [gentoo-embedded] e2fsprogs checking for blkid_get_cache in -lblkid... no Kfir Lavi
2011-01-03 18:41 ` Mike Frysinger
2011-01-04  9:02   ` Patrice Tisserand
2011-01-04 18:59     ` Mike Frysinger
2011-01-04 22:12       ` Patrice Tisserand
2011-01-05  7:03         ` Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox