From: ninevoltz at uclibc.org <ninevoltz@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/fontconfig
Date: Thu, 1 May 2008 12:01:11 -0700 (PDT) [thread overview]
Message-ID: <20080501190111.6360A3C67D@busybox.net> (raw)
Author: ninevoltz
Date: 2008-05-01 12:01:10 -0700 (Thu, 01 May 2008)
New Revision: 21911
Log:
remove libdir-la.patch, handled by Makefile.autotools.in
Removed:
trunk/buildroot/package/fontconfig/fontconfig-2.4.2-libdir-la.patch
Changeset:
Deleted: trunk/buildroot/package/fontconfig/fontconfig-2.4.2-libdir-la.patch
===================================================================
--- trunk/buildroot/package/fontconfig/fontconfig-2.4.2-libdir-la.patch 2008-05-01 17:15:35 UTC (rev 21910)
+++ trunk/buildroot/package/fontconfig/fontconfig-2.4.2-libdir-la.patch 2008-05-01 19:01:10 UTC (rev 21911)
@@ -1,77 +0,0 @@
---- fontconfig/ltmain.sh.orig 2006-04-20 08:27:27.000000000 -0600
-+++ fontconfig/ltmain.sh 2007-01-13 14:26:01.000000000 -0700
-@@ -273,8 +273,9 @@
- # line option must be used.
- if test -z "$tagname"; then
- $echo "$modename: unable to infer tagged configuration"
-- $echo "$modename: specify a tag with \`--tag'" 1>&2
-- exit $EXIT_FAILURE
-+ $echo "$modename: defaulting to \`CC'"
-+ $echo "$modename: if this is not correct, specify a tag with \`--tag'"
-+# exit $EXIT_FAILURE
- # else
- # $echo "$modename: using $tagname tagged configuration"
- fi
-@@ -2404,8 +2405,14 @@
- absdir="$abs_ladir"
- libdir="$abs_ladir"
- else
-- dir="$libdir"
-- absdir="$libdir"
-+ # Adding 'libdir' from the .la file to our library search paths
-+ # breaks crosscompilation horribly. We cheat here and don't add
-+ # it, instead adding the path where we found the .la. -CL
-+ dir="$abs_ladir"
-+ absdir="$abs_ladir"
-+ libdir="$abs_ladir"
-+ #dir="$libdir"
-+ #absdir="$libdir"
- fi
- test "X$hardcode_automatic" = Xyes && avoidtemprpath=yes
- else
-@@ -2886,6 +2893,16 @@
- esac
- if grep "^installed=no" $deplib > /dev/null; then
- path="$absdir/$objdir"
-+# This interferes with crosscompilation. -CL
-+# else
-+# eval libdir=`${SED} -n -e 's/^libdir=\(.*\)$/\1/p' $deplib`
-+# if test -z "$libdir"; then
-+# $echo "$modename: \`$deplib' is not a valid libtool archive" 1>&2
-+# exit 1
-+# fi
-+# if test "$absdir" != "$libdir"; then
-+# $echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
-+# fi
- else
- eval libdir=`${SED} -n -e 's/^libdir=\(.*\)$/\1/p' $deplib`
- if test -z "$libdir"; then
-@@ -5598,6 +5615,10 @@
- # Replace all uninstalled libtool libraries with the installed ones
- newdependency_libs=
- for deplib in $dependency_libs; do
-+ # Replacing uninstalled with installed can easily break crosscompilation,
-+ # since the installed path is generally the wrong architecture. -CL
-+ newdependency_libs="$newdependency_libs $deplib"
-+ continue
- case $deplib in
- *.la)
- name=`$echo "X$deplib" | $Xsed -e 's%^.*/%%'`
-@@ -5919,10 +5940,13 @@
- # At present, this check doesn't affect windows .dll's that
- # are installed into $libdir/../bin (currently, that works fine)
- # but it's something to keep an eye on.
-- if test "$inst_prefix_dir" = "$destdir"; then
-- $echo "$modename: error: cannot install \`$file' to a directory not ending in $libdir" 1>&2
-- exit $EXIT_FAILURE
-- fi
-+ #
-+ # This breaks install into our staging area. -PB
-+ #
-+ # if test "$inst_prefix_dir" = "$destdir"; then
-+ # $echo "$modename: error: cannot install \`$file' to a directory not ending in $libdir" 1>&2
-+ # exit $EXIT_FAILURE
-+ # fi
-
- if test -n "$inst_prefix_dir"; then
- # Stick the inst_prefix_dir data into the link command.
next reply other threads:[~2008-05-01 19:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:01 ninevoltz at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-10 13:47 [Buildroot] svn commit: trunk/buildroot/package/fontconfig thomasez at uclibc.org
2008-12-22 22:10 jacmet at uclibc.org
2008-11-11 19:38 tpetazzoni at uclibc.org
2008-09-14 19:35 jacmet at uclibc.org
2008-08-16 19:13 jacmet at uclibc.org
2008-06-26 14:04 jacmet at uclibc.org
2008-03-06 18:09 ninevoltz at uclibc.org
2007-08-12 12:06 ulf at uclibc.org
2007-08-10 14:44 ulf at uclibc.org
2007-07-23 8:18 ulf at uclibc.org
2007-06-28 14:03 aldot at uclibc.org
2007-05-24 8:41 jacmet at uclibc.org
2007-05-22 10:31 jacmet at uclibc.org
2007-02-03 20:52 andersen at uclibc.org
2007-01-29 12:59 aldot at uclibc.org
2007-01-16 16:06 aldot at uclibc.org
2007-01-16 8:10 andersen at uclibc.org
2007-01-15 21:26 andersen at uclibc.org
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=20080501190111.6360A3C67D@busybox.net \
--to=ninevoltz@uclibc.org \
--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