From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc-error with latest buildroot
Date: Sat, 26 Dec 2009 09:16:48 -0600 [thread overview]
Message-ID: <200912260916.50648.minimod@morethan.org> (raw)
In-Reply-To: <200912261558.18888.marco-glatz@web.de>
On Sat December 26 2009, Marco Glatz wrote:
> > 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.
>
>
> hi,
>
> with fortran enabled, the --with-mpfr and --with-gmp get set, but still
> doesn'nt work.
>
> i found this:
>
> http://dvb-community.de/wiki/index.php/GCC-uClibC_Toolchain_erstellen
>
> and this:
>
> http://downloads.openwrt.org/docs/buildroot-documentation.html
>
Been following OpenWRT (and OpenEmbedded) for several years;
I may have to switch to OpenWRT's build system myself.
I really don't need something that can build an entire distribution -
But at least those projects do have more people on the maintenance staff.
Will be postponing my own decision until I finish putting full MIPS support
into 2009.11 - I don't think I want to tackle the Makefile code churn here
to also put that support into dev-head.
Mike
>
>
> i will give it a try. also tried scratchbox, but that din't work either.
>
>
> marco
>
>
next prev parent reply other threads:[~2009-12-26 15:16 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
[not found] ` <200912261558.18888.marco-glatz@web.de>
2009-12-26 15:16 ` Michael S. Zick [this message]
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=200912260916.50648.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.