From: fpml at adinet.com.uy <fpml@adinet.com.uy>
To: buildroot@busybox.net
Subject: [Buildroot] libtool, libglib2, *_HOOK_POST_(BUILD|INSTALL)
Date: Sun, 13 Apr 2008 01:28:11 -0300 (UYT) [thread overview]
Message-ID: <27218521.1208060891367.JavaMail.tomcat@fe-ps02> (raw)
target: x86 uclibc/busybox
(1) libtool built by many packages use system paths to find shared-
objects, producing libraries that don't work on target.
I'm using this shell script to patch libtool after configure:
#!/bin/sh
sed 's/sys_lib_search_path_spec=\"[^\"]*\"/sys_lib_search_path_spec=\"
\"/' $1 >/tmp/sedtmp1
sed 's/sys_lib_dlsearch_path_spec=\"[^\"]*\"
/sys_lib_dlsearch_path_spec=\"\"/' /tmp/sedtmp1 >/tmp/sedtmp2
#sed 's/shlibpath_var=LD_LIBRARY_PATH/shlibpath_var=\"\"/'
/tmp/sedtmp2 >/tmp/sedtmp3
mv /tmp/sedtmp2 $1
chmod +x $1
(2) libglib2 builds some libs that use shared-objects from host
system, even after patching its libtool.
eg gmodule/.libs/libgmodule-2.0.so.0.1504.0 << works
gmodule/.libs/libgmodule-2.0.so.0.1504.0T << host libs
Good one copied to staging, while the other goes to project_*, so
binaries on the final image fail to run due to missing libs (eg instead
of uclibc's libc.so.0, libgmodule requests libc.so.6 present in my
Slackware host)
(3) How does one use {pkgname}_HOOK_POST_BUILD and INSTALL? I tried
to use it on libglib2's mk but looks like it is ignored.
Thanks,
Fernando.
reply other threads:[~2008-04-13 4:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=27218521.1208060891367.JavaMail.tomcat@fe-ps02 \
--to=fpml@adinet.com.uy \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox