Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Various problem using buildroot-2012.05
Date: Sat, 10 Nov 2012 16:51:41 +0200	[thread overview]
Message-ID: <509E69FD.2000804@petroprogram.com> (raw)
In-Reply-To: <qaol7k.eta.ln@bernd-kuhls.de>

Hi Bernd

10.11.2012 16:28, Bernd Kuhls kirjoitti:
> Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8
> @public.gmane.org> wrote in news:20120618103657.721db39b at skate:
>
>> Le Mon, 18 Jun 2012 00:46:05 -0700 (PDT),
>> Ming-Ching Tiew <mctiew@yahoo.com> a ??crit :
>>> Because there are many packages are not made to compile in a cross
>>> environment. For many, it's not a trial task to adapt those packages
>>> for cross compiling. 
>> Which packages are you talking about? If there are of general interest,
>> some people might be interested in helping to get them to cross-compile.
> Hi,
>
> in my case it?s Perl, along with Spamassassin to be build on-top of it. The 
> current effort to cross-compile Perl is problematic in regard to cross-
> compile CPAN modules, so now I am trying to compile Perl on the target 
> machine using a buildroot-made gcc_target toolchain along with some 
> dependency libs.

Yes, Perl is a (as you can see from various patches and problems related
to perl in this mailing list) is a really
major PITA to cross-compile.

If you try to use buildroot-made target gcc to compile perl, that is,
you use buildroot to cross-compile gcc to run natively inside
uClibc (?) environment, then you might encounter problems.

As Thomas has said in few times here for people telling about problems
of native gcc-toolchain, buildroot is about cross-compiling stuff
and buildroot produced native gcc-toolchain is really not supported and
might be still broken
(I don't know what the current status of it is now).

I remember that I promised to Thomas to investigate the native gcc for
x86 (under uClibc) thing and the only solution I have so far
managed to cook is by making a completely self-sustaining, buildroot
independent environment with working perl 5.16, python 2.7,
gcc 4.7, binutils 2.22 and lot's of other stuff. I decided to use RPM
for package management and spend healthy amount of three
weekends of studying how to make RPMs.

Maybe, when I have more time, I will compare my working native uClibc
gcc-toolchain and buildroot produced native uClibc gcc-toolchain
and cook some patches.

In case that buildroot produced native toolchain won't work, I will be
happy to send you my native uClibc-based gcc-toolchain
that you can chroot into, and see if that is of any help.

Mind you that it's still in beta-phase...

Best Regards
Stefan

> Kind regards, Bernd
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121110/080ae49e/attachment.html>

  reply	other threads:[~2012-11-10 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  7:46 [Buildroot] Various problem using buildroot-2012.05 Ming-Ching Tiew
2012-06-18  8:36 ` Thomas Petazzoni
2012-11-10 14:28   ` Bernd Kuhls
2012-11-10 14:51     ` Stefan Fröberg [this message]
2012-11-10 20:21       ` Bernd Kuhls
2012-11-11 22:47       ` Arnout Vandecappelle
2012-11-12  0:04         ` Stefan Fröberg
2012-11-12  7:36           ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2012-06-18  3:35 Ming-Ching Tiew
2012-06-18  5:55 ` Ming-Ching Tiew
2012-06-18  6:45 ` Thomas Petazzoni

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=509E69FD.2000804@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --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