From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc-error with latest buildroot
Date: Sat, 26 Dec 2009 08:29:54 -0600 [thread overview]
Message-ID: <200912260829.56765.minimod@morethan.org> (raw)
In-Reply-To: <200912261520.40706.marco-glatz@web.de>
On Sat December 26 2009, Marco Glatz wrote:
> Am Samstag, 26. Dezember 2009 15:08:53 schrieb Michael S. Zick:
> > On Sat December 26 2009, Marco Glatz wrote:
> > > hello,
> > >
> > > i'm trying to make a toolchain using latest buildroot, but when compiling
> > > gcc i get this error:
> > >
> > > checking for correct version of gmp.h... yes
> > > checking for correct version of mpfr.h... no
> >
> > This problem shipped in 2009.11 also -
> > Fails even if mpfr is put into the GCC tree -
> >
> > Looks like it might be tied in with the logic of building Fortran -
> > (GCC once only used mpfr on the Fortran builds).
> > Haven't had time for further testing myself.
> >
> > There is what might be a related bug report already posted.
>
>
> hi,
>
> this helped me out:
>
> http://www.linuxquestions.org/questions/linux-from-scratch-13/i-have-an-error-
> building-gcc-requires-gmp-4.1-and-mpfr-2.3.0.-690426/
>
> so i put gmp and mpfr directories in the gcc-folder in the output/toolchain-
> directory. then it compiled. later when linking there were a lot of errors not
> finding gmp-related functions, so i put again mpfr and gmp in output/build/gcc-
> x-x-target directory. but that didn't help, still getting lot of undefined
> reference to __gmpz_* functions.
>
> all the pages i found on google said you should configure --with-mpfr=... and
> --with-gmp=....., and there are options fpr this in the makefiles, but they do
> net get filled.
>
When I looked at it a month or so ago (prior to 2009.11 release) -
It looked to me as if filling those options where conditionalized
based on building Fortran. But I have about zero Makefile knowledge.
Try enabling Fortran compiler in the build, it might "just work".
The Buildroot project uses a "tag-it, forget-it and move-on" release cycle;
they aren't staffed to support anything like a mission-critical,
stable release, version of Buildroot.
Mike
>
> marco
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
next prev parent reply other threads:[~2009-12-26 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 13:27 [Buildroot] gcc-error with latest buildroot Marco Glatz
2009-12-26 14:08 ` Michael S. Zick
2009-12-26 14:20 ` Marco Glatz
2009-12-26 14:29 ` Michael S. Zick [this message]
[not found] ` <200912261558.18888.marco-glatz@web.de>
2009-12-26 15:16 ` Michael S. Zick
2009-12-26 17:36 ` Thomas Petazzoni
2009-12-26 17:42 ` Michael S. Zick
2009-12-26 19:58 ` Michael S. Zick
2009-12-26 21:18 ` Thomas Petazzoni
2009-12-26 21:39 ` Michael S. Zick
2009-12-26 22:11 ` Michael S. Zick
2009-12-26 20:40 ` Marco Glatz
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=200912260829.56765.minimod@morethan.org \
--to=minimod@morethan.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