From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] Fontconfig/freetype build searches for lmxl2 in system /usr/lib b4 searching in staging_dir/usr/lib
Date: Tue, 17 Jul 2007 04:37:53 -0700 (PDT) [thread overview]
Message-ID: <11647587.post@talk.nabble.com> (raw)
Dear all,
while building fontconfig/freetype, i found that -lxml2 is taken from
system /usr/lib whereas it is suppose to take from staging_dir/usr/lib. when
it is checking for -lxml2 it 1st searched from system /usr/lib & gave error
as invalid file format. i renamed the one in system /usr/lib to
old_libxml2.so & then "make fontconfig" went on taking -lxml2 from
staging_dir/usr/lib. so i doubt many files like this are taken from system
/usr/lib than from staging_dir/usr/lib. kindly let me know if i need any
changes/updates.
sorry for double post. just wanted to split and make subject more clear.
Regards
Gururaja
--
View this message in context: http://www.nabble.com/Fontconfig-freetype-build-searches-for-lmxl2-in-system--usr-lib-b4-searching-in-staging_dir-usr-lib-tf4096288.html#a11647587
Sent from the BuildRoot mailing list archive at Nabble.com.
reply other threads:[~2007-07-17 11:37 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=11647587.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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