Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2623] New: buildroot-snapshot-20100922 fails when compiling development packages to target
Date: Wed, 22 Sep 2010 10:19:38 +0000 (UTC)	[thread overview]
Message-ID: <bug-2623-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=2623

           Summary: buildroot-snapshot-20100922 fails when compiling
                    development packages to target
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: tselmeci at open-st.eu
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 2527
  --> https://bugs.busybox.net/attachment.cgi?id=2527
buildroot-20100922 config file

I'm using the latest snapshot of buildroot (buildroot-20100922) on Arch Linux.
Target is an ARM (Xscale) machine, what I need is only the toolchain. Toolchain
is generated without any problem.

I'd need a native toolchain on the ARM machine, which runs on ARM and creates
output for the ARM machine. Buildroot seems to support this. These are switched
on under "Package Selection for the Target --> Development tools":
-  native toolchain in the target filesystem;
- gmp;
- gmp headers;
- make;
- mpfr;
- mpfr headers;
- libtool;

See the attached file for the exact buildroot configuration I've been using.

Buildroot stops compiling native toolchain with the following error:

-------------------------------------------------------------
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether gcc __attribute__ ((mode (XX))) works... yes
checking for recent GMP... yes
checking for gmp internal files... no
checking for working alloca.h... yes
checking for alloca... yes
checking for __gmpz_init in -lgmp... no
configure: error: libgmp not found or uses a different ABI.
Please read the INSTALL file -- see "In case of problem".
make[1]: ***
[/home/tselmeci/repos/uah/uah.169/trunk/packages/buildroot/buildroot-20100922-tools/output/build/mpfr-2.4.1/.configured]
Error 1
make[1]: Leaving directory
`/home/tselmeci/repos/uah/uah.169/trunk/packages/buildroot/buildroot-20100922-tools'
make: *** [.DEFAULT] Error 2
-------------------------------------------------------------

I made several attempts with buildroot-2010.08, buildroot-2010.05 and with this
daily snapshot, but regardless of gcc selection, EABI/OABI, it always failed.

Please have a look at the problem, thanks!

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-09-22 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 10:19 bugzilla at busybox.net [this message]
2011-02-02 15:49 ` [Buildroot] [Bug 2623] buildroot-snapshot-20100922 fails when compiling development packages to target bugzilla at busybox.net

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=bug-2623-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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