All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Non-x86 support question
Date: Thu, 26 Nov 2009 22:36:23 +0100	[thread overview]
Message-ID: <87zl696ka0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200911261521.32631.minimod@morethan.org> (Michael S. Zick's message of "Thu\, 26 Nov 2009 15\:21\:30 -0600")

>>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:

 Michael> Just wondering, does buildroot get tested as a cross-compiler
 Michael> building native toolchain?

The BR2_PACKAGE_GCC_TARGET? No, that isn't commonly used. That doesn't
mean that it shouldn't work ofcourse.

 Michael> There is a similar bug posted, which I think refers to building
 Michael> the foreign, native, compiler.
 Michael> At least that is my own problem.  ;)

 Michael> In my case, gcc's configure is failing when it tries to test for
 Michael> the presence of mpfr (which is present, and built) - - -
 Michael> (No problem with gpm) 

Hmm, it worked for me last time I tried (some time this summer).

 Michael> I have captured the configure command being run and the test file,
 Michael> then ran them "by hand" with -v the best I can figure out at
 Michael> that point is:

Could you provide a bit more details? What goes wrong?

 Michael> A true puzzle, not a show-stopper here, anytime by 2010.02
 Michael> would be fine.  This is gcc-4.3.whatever targeting mipsel.

It would be good if you could add a bugreport to bugzilla so we don't
forget about it.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-11-26 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 21:21 [Buildroot] Non-x86 support question Michael S. Zick
2009-11-26 21:36 ` Peter Korsgaard [this message]
2009-11-27 12:30   ` Michael S. Zick

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=87zl696ka0.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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.