Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril HAENEL <chaenel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot compilation blocks on LZO package
Date: Tue, 20 Jan 2009 15:57:30 +0100	[thread overview]
Message-ID: <4975E65A.30901@free.fr> (raw)
In-Reply-To: <87bpu2w0n3.fsf@macbook.be.48ers.dk>



Peter Korsgaard a ?crit :
>>>>>> "Cyril" == Cyril HAENEL <chaenel@free.fr> writes:
>>>>>>             
>
>  Cyril> Hi all,
>  Cyril> I try to build a rootfs based on 
>  Cyril> http://buildroot.uclibc.org/downloads/buildroot-2009.02-rc1.tar.gz
>
>  Cyril> After unpacking, I done make menuconfig and done very small things :
>
>  Cyril> - Put Target Architecture to Arm
>  Cyril> - Put Target Architecture variant tp generic_arm
>  Cyril> - Put Filesystem for target device to jffs2, and not ext2
>
>  Cyril> After that, a make the build works well until it reach the LZO package.
>  Cyril> The configure script blocks on this line :
>
>  Cyril> checking whether we are using the GNU C++ compiler...
>
> Strange, it works here (powerpc):
>
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
>
> Please send you .config file.
>
>   
Peter, you will my config attached

I don't know what happen because until lzo package, everything is built 
successfully !

Regards

-- 

Cyril Haenel
Registered Linux User #332632

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config.txt
Url: http://lists.busybox.net/pipermail/buildroot/attachments/20090120/22db80df/attachment-0001.txt 

      reply	other threads:[~2009-01-20 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 13:35 [Buildroot] Buildroot compilation blocks on LZO package Cyril HAENEL
2009-01-20 13:46 ` Peter Korsgaard
2009-01-20 14:57   ` Cyril HAENEL [this message]

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=4975E65A.30901@free.fr \
    --to=chaenel@free.fr \
    --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