From: David Thomas <davelists2@peoplemerge.com>
To: gentoo-dev@lists.gentoo.org, gentoo-embedded@lists.gentoo.org
Subject: [gentoo-dev] problems crosscompiling libXt
Date: Sat, 17 Dec 2005 18:20:33 -0500 [thread overview]
Message-ID: <20051217232033.GA24919@peoplemerge.com> (raw)
Hey all,
Here is a fix for libXt, similar to the problems I had with libX11
last week. I don't see an obvious way to patch the Makefile.am.
Please send comments.
Symptom:
../util/makestrs -i .. < ../util/string.list > StringDefs.c
/bin/sh: ../util/makestrs: cannot execute binary file
make[2]: *** [StringDefs.c] Error 126
For this to work, have a look at the ebuild in the forwarded msg.
Fix patchfile:
--- util/Makefile.in
+++ util/Makefile.in
@@ -48,7 +48,7 @@
AUTOHEADER = @AUTOHEADER@
AUTOMAKE = @AUTOMAKE@
AWK = @AWK@
-CC = @CC@
+CC = gcc
CCDEPMODE = @CCDEPMODE@
CFLAGS = @CFLAGS@
CPP = @CPP@
On Fri, Dec 09, 2005 at 03:19:28AM -0500, David Thomas (davelists2@peoplemerge.com) wrote:
Subject: [gentoo-embedded] problems crosscompiling libX11
Message ID: <20051209081928.GA11683@peoplemerge.com>
> I've been having problems with libX11. First it tries to build a binary
> with the crosscompiler then execute it:
>
> /bin/sh: ../src/util/makekeys: cannot execute binary file
>
> I wrote a patch that fixes this... See below.
>
> I'm still having a problem with libtool. The last step of the build process
> it does the following:
> /bin/sh ../libtool --mode=link armv5l-softfloat-linux-uclibc-gcc ... -L /newroot/usr/lib ...
> ...(much more)... -lXau -lXdmcp -ldl
>
> This calls the crosscompiler replacing -lXau and -lXdmcp with /usr/lib/libXau.so and
> /usr/lib/libXdmcp.so INSTEAD of the crosscompiled ones in /newroot/usr/lib
>
> Same thing even if I hardcode values in ../libtool for sys_lib_search_path_spec.
> I also tried setting an LDPATH in /etc/env.d/05crosscompiler.
>
> Am I missing something in /etc/ld.so.conf environment?
>
> Thanks!
> Dave Thomas
>
> Here are the fixes:
> Added to ebuild (is this right? comments? it seems to work):
> src_unpack()
> {
> x-modular_unpack_source
> x-modular_patch_source
> cd ${S}
> epatch /path/to/patchfile
> x-modular_reconf_source
> }
>
> patchfile:
> --- src/util/Makefile.am
> +++ src/util/Makefile.am
> @@ -4,7 +4,8 @@
>
> makekeys_CFLAGS=$(X11_CFLAGS) $(BIGREQS_CFLAGS)
>
> -#override CC = gcc
> +#do not override CC, this is needed when using a crosscompiler since this executable is to be run on $build not $host
> +CC = gcc
> LINK = $(CC) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
>
> EXTRA_DIST = mkks.sh
> --- src/util/Makefile.in
> +++ src/util/Makefile.in
> @@ -189,8 +189,9 @@
>
> makekeys_CFLAGS = $(X11_CFLAGS) $(BIGREQS_CFLAGS)
>
> -#override CC = gcc
> +#no, do not override CC, this is needed when using a crosscompiler since this executable is to be run on $build not $host
> +CC = gcc
> LINK = $(CC) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
>
> __END__
>
>
>
> --
> gentoo-embedded@gentoo.org mailing list
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-12-17 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 23:20 David Thomas [this message]
2005-12-18 1:37 ` [gentoo-dev] problems crosscompiling libXt Mike Frysinger
2005-12-19 5:24 ` Mike Frysinger
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=20051217232033.GA24919@peoplemerge.com \
--to=davelists2@peoplemerge.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
/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