public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Vladimir Pouzanov" <farcaller@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] cross-compile readline
Date: Sun, 22 Oct 2006 15:24:57 +0300	[thread overview]
Message-ID: <9956e0d30610220524y43832fb2ve9ee6640d7730543@mail.gmail.com> (raw)

Hi all,

I can't cross-compile readline for arm (arm-softfloat-linux-gnu):
>>> Emerging (1 of 4) sys-libs/readline-5.2 to /usr/arm-softfloat-linux-gnu/
 * readline-5.2.tar.gz MD5 ;-) ... [ ok ]
 * readline-5.2.tar.gz RMD160 ;-) ... [ ok ]
 * readline-5.2.tar.gz SHA1 ;-) ...   [ ok ]
 * readline-5.2.tar.gz SHA256 ;-) ...  [ ok ]
 * readline-5.2.tar.gz size ;-) ...  [ ok ]
>>> Unpacking source...
>>> Unpacking readline-5.2.tar.gz to /var/tmp/portage/sys-libs/readline-5.2/work
 * Applying readline-5.0-no_rpath.patch ...  [ ok ]
 * Applying readline-5.2-rlfe-build.patch ...  [ ok ]
 * Applying readline-5.1-rlfe-uclibc.patch ...   [ ok ]
 * Applying readline-5.1-fbsd-pic.patch ...  [ ok ]
>>> Source unpacked.
>>> Compiling source in
/var/tmp/portage/sys-libs/readline-5.2/work/readline-5.2 ...
 * econf: updating readline-5.2/support/config.guess with
/usr/share/gnuconfig/config.guess
 * econf: updating readline-5.2/support/config.sub with
/usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=arm-softfloat-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --with-curses
--libdir=/usr/lib --build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... arm-softfloat-linux-gnu
configure: cross-compiling for arm-softfloat-linux-gnu is not supported

Beginning configuration for readline-5.2 for arm-softfloat-linux-gnu

checking whether make sets $(MAKE)... yes
checking for arm-softfloat-linux-gnu-gcc... arm-softfloat-linux-gnu-gcc
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-libs/readline-5.2/work/readline-5.2/config.log

!!! ERROR: sys-libs/readline-5.2 failed.
Call stack:
  ebuild.sh, line 1568:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  readline-5.2.ebuild, line 60:   Called econf '--with-curses'
'--libdir=/usr/lib'
  ebuild.sh, line 540:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call
stack if relevant.

from config.log:
configure:1880: checking for C compiler default output file name
configure:1883: arm-softfloat-linux-gnu-gcc -g   conftest.c  >&5
/usr/libexec/gcc/arm-softfloat-linux-gnu/ld: crt1.o: No such file: No
such file or directory
collect2: ld returned 1 exit status

Any ideas?

PS: crt1.o is at /usr/arm-softfloat-linux-gnu/usr/lib/crt1.o

-- 
Sincerely,
Vladimir "Farcaller" Pouzanov
http://www.hackndev.com
-- 
gentoo-embedded@gentoo.org mailing list



             reply	other threads:[~2006-10-22 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22 12:24 Vladimir Pouzanov [this message]
2006-10-22 17:39 ` [gentoo-embedded] cross-compile readline Daniel Glaser
2006-10-22 17:44   ` Vladimir Pouzanov

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=9956e0d30610220524y43832fb2ve9ee6640d7730543@mail.gmail.com \
    --to=farcaller@gmail.com \
    --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