[Buildroot] build problems

[Buildroot] build problems

[Steve Calfee]

----- Original Message ----
> From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
> To: Steve Calfee <nospamcalfee@yahoo.com>
> Sent: Tuesday, March 4, 2008 4:21:09 PM
> Subject: Re: [Buildroot] build problems
> 
> Hi, I am continually having problems building.
> > I have the latest svn sources.
> > 
> > Does anybody know which of the arm926 projects ie xxxx_defconfig currently is 
> buildable. I would like to get an existing build to work before I customize it. 
> I am running on ubuntu Feisty.
> > 
> > As a second question, if I wish to change the package selection, do I need to 
> do a make clean? or will another make only deal with the current package 
> selections? If I do a make menuconfig, does it blitz the existing .config back 
> to defaults, or can I change packages at will starting with whatever prebuilt 
> xxx-defconfig I used?
> > 
> > Thanks, Steve
> > 
> > 
> 
> 
> I think that 
> 
> $ touch .config
> $ make at91sam9260dfc_defconfig
> $ make
> 
> should complete the build, but it was some time
> since I downloaded to a target, so I do not know if it will run.
> 
> I run OpenSuSE 10.2
> 

Thanks for the help. I had tried that before. the file package download site version had changed and I fixed that. Now when I do the build I get:

gzip -d -c /usr/local/install/downloads/libdaemon-0.12.tar.gz | tar -C /home/calfee/buildroot/arm/buildroot/build_arm   -xf -
toolchain/patch-kernel.sh /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12 package/libdaemon/ \*.patch

Applying libdir-la.patch using plaintext: 
patching file ltmain.sh
Hunk #1 succeeded at 273 (offset 42 lines).
Hunk #2 succeeded at 2408 with fuzz 2 (offset 128 lines).
Hunk #3 succeeded at 2896 (offset 135 lines).
Hunk #4 succeeded at 5623 (offset 465 lines).
Hunk #5 succeeded at 5948 (offset 468 lines).

Applying xcompile-setpgrp.patch using plaintext: 
patching file configure.ac
cp -f package/gnuconfig/config.sub package/gnuconfig/config.guess /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12
touch /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12/.unpacked
(cd /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12 && rm -rf config.cache && autoreconf)
configure.ac:41: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
make: *** [/home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12/.configured] Error 1
calfee at squiggy-linux:~/buildroot/arm/buildroot$ 


I have tried several other defconfig packages, and they all seem to have their own peculiar failures. This failed after the busybox build, so I guess it is a selected package. I know you don't have time to diagnose my problem, that is why I am looking for someone who has a recent arm926 package building with pure buildroot files. Maybe there isn't any?

Thanks for the suggestion, Steve




      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

[Buildroot] build problems

[Ulf Samuelsson]

> ----- Original Message ----
>> From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
>> To: Steve Calfee <nospamcalfee@yahoo.com>
>> Sent: Tuesday, March 4, 2008 4:21:09 PM
>> Subject: Re: [Buildroot] build problems
>> 
>> Hi, I am continually having problems building.
>> > I have the latest svn sources.
>> > 
>> > Does anybody know which of the arm926 projects ie xxxx_defconfig currently is 
>> buildable. I would like to get an existing build to work before I customize it. 
>> I am running on ubuntu Feisty.
>> > 
>> > As a second question, if I wish to change the package selection, do I need to 
>> do a make clean? or will another make only deal with the current package 
>> selections? If I do a make menuconfig, does it blitz the existing .config back 
>> to defaults, or can I change packages at will starting with whatever prebuilt 
>> xxx-defconfig I used?
>> > 
>> > Thanks, Steve
>> > 
>> > 
>> 
>> 
>> I think that 
>> 
>> $ touch .config
>> $ make at91sam9260dfc_defconfig
>> $ make
>> 
>> should complete the build, but it was some time
>> since I downloaded to a target, so I do not know if it will run.
>> 
>> I run OpenSuSE 10.2
>> 
> 
> Thanks for the help. I had tried that before. the file package download site version had changed and I fixed that. Now when I do the build I get:
> 
> gzip -d -c /usr/local/install/downloads/libdaemon-0.12.tar.gz | tar -C /home/calfee/buildroot/arm/buildroot/build_arm   -xf -
> toolchain/patch-kernel.sh /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12 package/libdaemon/ \*.patch
> 
> Applying libdir-la.patch using plaintext: 
> patching file ltmain.sh
> Hunk #1 succeeded at 273 (offset 42 lines).
> Hunk #2 succeeded at 2408 with fuzz 2 (offset 128 lines).
> Hunk #3 succeeded at 2896 (offset 135 lines).
> Hunk #4 succeeded at 5623 (offset 465 lines).
> Hunk #5 succeeded at 5948 (offset 468 lines).
> 
> Applying xcompile-setpgrp.patch using plaintext: 
> patching file configure.ac
> cp -f package/gnuconfig/config.sub package/gnuconfig/config.guess /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12
> touch /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12/.unpacked
> (cd /home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12 && rm -rf config.cache && autoreconf)
> configure.ac:41: error: possibly undefined macro: AC_PROG_LIBTOOL
>      If this token and others are legitimate, please use m4_pattern_allow.
>      See the Autoconf documentation.
> autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
> make: *** [/home/calfee/buildroot/arm/buildroot/build_arm/libdaemon-0.12/.configured] Error 1
> calfee at squiggy-linux:~/buildroot/arm/buildroot$ 
> 
> 
> I have tried several other defconfig packages, and they all seem to have their own peculiar failures. This failed after the busybox build, so I guess it is a selected package. I know you don't have time to diagnose my problem, that is why I am looking for someone who has a recent arm926 package building with pure buildroot files. Maybe there isn't any?
> 
> Thanks for the suggestion, Steve
> 


I think this is more the PC configuration.
You may have to upgrade your Autotools.


Best Regards
Ulf Samuelsson

[Buildroot] build problems

[Tim Barr]

FYI, when I modified the buildroot config to generate a uImage file, it
could not find the file so it could copy it into the binaries directory.
Looking at the log file, builroot was looking for the uImage file in the
"kernel" root directory instead of the "kernel"/arch/arm/boot directory.
At least I know where to find the uImage file so I can test it.

cp -dpf
/home/falingtrea/buildroot/project_build_arm/SuperModem-2.6.22.1/linux-2
.6.22.1/uImage
/home/falingtrea/buildroot/binaries/SuperModem-2.6.22.1/at91sam9260dfc-l
inux-2.6.22.1-20080326

Should be:

cp -dpf
/home/falingtrea/buildroot/project_build_arm/SuperModem-2.6.22.1/linux-2
.6.22.1/arch/arm/boot/uImage
/home/falingtrea/buildroot/binaries/SuperModem-2.6.22.1/at91sam9260dfc-l
inux-2.6.22.1-20080326


Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
tbarr at multitech.com

[Buildroot] build problems

[Tim Barr]

> -----Original Message-----
> From: Ulf Samuelsson [mailto:ulf.samuelsson at atmel.com] 
> Sent: Tuesday, March 25, 2008 5:42 PM
> To: Tim Barr; Buildroot List
> Subject: Re: [Buildroot] build problems
> 
> 
> Yes, but your development would be much easier if you got 
> a few free samples of an AT45DCB008D Dataflashcard.
> 
Only one possible problem I see with this. Looking at the 9260EK board,
there is a 0 ohm resistor(R42) connecting SPI0_CLK and MCCLK. I am
assuming this is there so that a DataFlash Card can be read from the SD
card slot. This also means that SPI0 has to be disabled after boot if
you want to use the SD card slot for SD cards. So if I want to be able
to us the SPI port for other devices, I have to remove that resistor
which makes the DataFlash card interface useless.

[Buildroot] build problems

[Ulf Samuelsson]

>> -----Original Message-----
>> From: Ulf Samuelsson [mailto:ulf.samuelsson at atmel.com] 
>> Sent: Tuesday, March 25, 2008 5:42 PM
>> To: Tim Barr; Buildroot List
>> Subject: Re: [Buildroot] build problems
>> 
>> 
>> Yes, but your development would be much easier if you got 
>> a few free samples of an AT45DCB008D Dataflashcard.
>> 
> Only one possible problem I see with this. Looking at the 9260EK board,
> there is a 0 ohm resistor(R42) connecting SPI0_CLK and MCCLK. I am
> assuming this is there so that a DataFlash Card can be read from the SD
> card slot. This also means that SPI0 has to be disabled after boot if
> you want to use the SD card slot for SD cards. So if I want to be able
> to us the SPI port for other devices, I have to remove that resistor
> which makes the DataFlash card interface useless.

Yes, there is an even more severe problem.
If you have an SD-Card inserted in the slot, it will be problematic
inserting a dataflash card at the same time ;-)


Best Regards
Ulf Samuelsson 

[Buildroot] build problems

[Tim Barr]

Well, I guess part of the problem is that there is no at91sam9260ek
directory in the target/device/atmel directory, even though there is a
at91sam9260ek target board selection in the buildroot .config file. The
two target directories available are at91sam9260dfc and at91sam9260pf. I
am not sure if the dfc means DataFlash card or chip, but the board could
use either I think. The card interface is CS_0 and the on-board chip is
CS_1. The board I have did not come with a DataFlash card so it has been
booting off of the on-board chip. So I assume I can use the dfc
defconfig but make sure the boot memory parameter in the config files is
set to CS_1. 

Also, when I run it right now and try to do a "make configured", I get
an error because it can't copy busybox-1.9.2.config. It looks like
busybox has been updated, but a new config file has not been put into
the target/device/atmel/at91sam9260dfc directory. So do I rename the
busybox-1.9.1.config file to busybox-1.9.2.config? Also, if I run "make
menuconfig" from the buildroot directory and look at the package
selection, busybox-1.9.x is selected. But the parameter 'busybox
configuration file to use' has '/package/busybox/busybox-1.6.0.config"
in it. Really confusing.

Some possibly good news, though. Using the at91sam9260dfc defconfig and
renaming the "busybox-1.9.1.config" file to "busybox-1.9.2.config" it
seems I finally completed a build. There are files in the binaries
directory of my project now. The linux kernel is 4mb so I assume it is
not a uImage, and I need to find where that setting is. Then I need to
see if it actually runs without panicking.

But, if I understand things correctly, the uboot and boot.bin files in
the binaries directory are for a EK board with a DataFlash card in the
SD slot, and would not work for the DataFlash chip on the board. I
wonder if I replaced the kernel and rfs files in the prebuilt binary
package I downloaded from Linux4Sam, I could get it to work? I will try
that when I get a chance.

Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
tbarr at multitech.com 

-----Original Message-----
From: buildroot-bounces@uclibc.org [mailto:buildroot-bounces at uclibc.org]
On Behalf Of John Voltz
Sent: Monday, March 24, 2008 7:52 AM
To: Buildroot List
Subject: Re: [Buildroot] build problems


Timothy,

What type of problems are you having with buildroot? What's failing for
you?

John Voltz


On Mon, Mar 24, 2008 at 8:45 AM, Tim Barr <tbarr@multitech.com> wrote:

I have had a similar problem, Steve. I wonder if any of the maintainers
has tried running buildroot after a dirclean recently? Or cleared out
the download directory to see if any package download interfaces have
changed? I have been trying to get a successful buildroot process (for
an AT91SAM9260EK) to complete for over 3 months now with no luck
whatsoever. I ended up having to buy a Timesys linuxlink license in
order to move forward.

Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
tbarr at multitech.com



> -----Original Message-----
> From: buildroot-bounces at uclibc.org
> [mailto:buildroot-bounces at uclibc.org] On Behalf Of Steve Calfee
> Sent: Sunday, March 23, 2008 10:51 AM
> To: buildroot at uclibc.org
> Subject: Re: [Buildroot] build problems
>
>
> Hi All,
>
> I used buildroot a couple of years ago successfully with a
> samsung 2410 soc.
>
> I am now trying to use it for a new project. My problem is I
> cannot get any build to work.
>
> Has anyone done a svn update and select a default config and
> have it build? I want to build an arm system, but first I
> would like some default config to build. I am using ubuntu
> feisty and think I have installed all the required tools. The
> mailing list seems to be quite active, but things seem to be
> in chaos. Can anyone tell me a starting place that is known to work?
>
> Thanks, Steve
>

[Buildroot] build problems

[Ulf Samuelsson]

> Well, I guess part of the problem is that there is no at91sam9260ek
> directory in the target/device/atmel directory, even though there is a
> at91sam9260ek target board selection in the buildroot .config file. The
> two target directories available are at91sam9260dfc and at91sam9260pf. I
> am not sure if the dfc means DataFlash card or chip, but the board could
> use either I think. The card interface is CS_0 and the on-board chip is
> CS_1. The board I have did not come with a DataFlash card so it has been
> booting off of the on-board chip. So I assume I can use the dfc
> defconfig but make sure the boot memory parameter in the config files is
> set to CS_1. 

Yes, but your development would be much easier if you got 
a few free samples of an AT45DCB008D Dataflashcard.

> 
> Also, when I run it right now and try to do a "make configured", I get
> an error because it can't copy busybox-1.9.2.config. It looks like
> busybox has been updated, but a new config file has not been put into
> the target/device/atmel/at91sam9260dfc directory. So do I rename the
> busybox-1.9.1.config file to busybox-1.9.2.config? 

I think this will work.
The problem is that people updating the busybox support,
disables the use of older busybox, which will force the 
saved config to update the version.
I am not sure that this is a good idea.

> Also, if I run "make
> menuconfig" from the buildroot directory and look at the package
> selection, busybox-1.9.x is selected. But the parameter 'busybox
> configuration file to use' has '/package/busybox/busybox-1.6.0.config"
> in it. Really confusing.
> 

Not sure, but I think this is overridden in the Atmel makefile.

> Some possibly good news, though. Using the at91sam9260dfc defconfig and
> renaming the "busybox-1.9.1.config" file to "busybox-1.9.2.config" it
> seems I finally completed a build. There are files in the binaries
> directory of my project now. The linux kernel is 4mb so I assume it is
> not a uImage, and I need to find where that setting is. Then I need to
> see if it actually runs without panicking.

It is probably set to "vmlinux" in the kernel configuration.

> 
> But, if I understand things correctly, the uboot and boot.bin files in
> the binaries directory are for a EK board with a DataFlash card in the
> SD slot, and would not work for the DataFlash chip on the board. I
> wonder if I replaced the kernel and rfs files in the prebuilt binary
> package I downloaded from Linux4Sam, I could get it to work? I will try
> that when I get a chance.

I hope so.

> 
> Timothy Barr
> Hardware Development Engineer
> for Multi-Tech Systems, Inc.
> tbarr at multitech.com 
> 
> -----Original Message-----
> From: buildroot-bounces at uclibc.org [mailto:buildroot-bounces at uclibc.org]
> On Behalf Of John Voltz
> Sent: Monday, March 24, 2008 7:52 AM
> To: Buildroot List
> Subject: Re: [Buildroot] build problems
> 
> 
> Timothy,
> 
> What type of problems are you having with buildroot? What's failing for
> you?
> 
> John Voltz
> 
> 
> On Mon, Mar 24, 2008 at 8:45 AM, Tim Barr <tbarr@multitech.com> wrote:
> 
> I have had a similar problem, Steve. I wonder if any of the maintainers
> has tried running buildroot after a dirclean recently? Or cleared out
> the download directory to see if any package download interfaces have
> changed? I have been trying to get a successful buildroot process (for
> an AT91SAM9260EK) to complete for over 3 months now with no luck
> whatsoever. I ended up having to buy a Timesys linuxlink license in
> order to move forward.
> 
> Timothy Barr
> Hardware Development Engineer
> for Multi-Tech Systems, Inc.
> tbarr at multitech.com
> 

Best Regards
Ulf Samuelsson

[Buildroot] build problems

[Peter Korsgaard]

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

Hi,

 >> Also, when I run it right now and try to do a "make configured", I get
 >> an error because it can't copy busybox-1.9.2.config. It looks like
 >> busybox has been updated, but a new config file has not been put into
 >> the target/device/atmel/at91sam9260dfc directory. So do I rename the
 >> busybox-1.9.1.config file to busybox-1.9.2.config? 

 Ulf> I think this will work.
 Ulf> The problem is that people updating the busybox support,
 Ulf> disables the use of older busybox, which will force the 
 Ulf> saved config to update the version.
 Ulf> I am not sure that this is a good idea.

I'll be the first to admit to not knowing anything about that 11MB
blob under target/device/Atmel  - Why make it so fragile to begin with?

By now all the avr/atmel stuff takes up around half the buildroot size
- I don't have access to any of that hardware, so I won't test it.

I see that the directory only has a busybox config for 1.6.1 and
1.9.1, so it's broken anyway if the user selects anything else than
that.

To me it doesn't make sense to keep earlier versions than the latest
stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)
- Otherwise it'll get too hard to handle. I think it's also soon time
to retire some of the really ancient versions like 1.2.x - 1.6.x.

 >> Also, if I run "make
 >> menuconfig" from the buildroot directory and look at the package
 >> selection, busybox-1.9.x is selected. But the parameter 'busybox
 >> configuration file to use' has '/package/busybox/busybox-1.6.0.config"
 >> in it. Really confusing.
 >> 

 Ulf> Not sure, but I think this is overridden in the Atmel makefile.

Yes, the target/device/Atmel hardcodes it to

BR2_PACKAGE_BUSYBOX_CONFIG:=$(BR2_BOARD_PATH)/busybox-$(BR2_BUSYBOX_VERSION).config

Which is bad.

-- 
Bye, Peter Korsgaard

[Buildroot] build problems

[Bernhard Fischer]

On Wed, Mar 26, 2008 at 12:11:21PM +0100, Peter Korsgaard wrote:
>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>
>Hi,
>
> >> Also, when I run it right now and try to do a "make configured", I get
> >> an error because it can't copy busybox-1.9.2.config. It looks like
> >> busybox has been updated, but a new config file has not been put into
> >> the target/device/atmel/at91sam9260dfc directory. So do I rename the
> >> busybox-1.9.1.config file to busybox-1.9.2.config? 
>
> Ulf> I think this will work.
> Ulf> The problem is that people updating the busybox support,
> Ulf> disables the use of older busybox, which will force the 
> Ulf> saved config to update the version.
> Ulf> I am not sure that this is a good idea.
>
>I'll be the first to admit to not knowing anything about that 11MB
>blob under target/device/Atmel  - Why make it so fragile to begin with?
>
>By now all the avr/atmel stuff takes up around half the buildroot size
>- I don't have access to any of that hardware, so I won't test it.
>
>I see that the directory only has a busybox config for 1.6.1 and
>1.9.1, so it's broken anyway if the user selects anything else than
>that.
>
>To me it doesn't make sense to keep earlier versions than the latest
>stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)
>- Otherwise it'll get too hard to handle. I think it's also soon time
>to retire some of the really ancient versions like 1.2.x - 1.6.x.

hehe, sounds familiar. I've already had my share of fun with Ulf in
exactly this area and consequently there is that git-repo which fixes
alot of this stuff for good.

cheers,

[Buildroot] build problems

[Peter Korsgaard]

>>>>> "Bernhard" == Bernhard Fischer <rep.dot.nop@gmail.com> writes:

Hi,

 >> To me it doesn't make sense to keep earlier versions than the latest
 >> stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)
 >> - Otherwise it'll get too hard to handle. I think it's also soon time
 >> to retire some of the really ancient versions like 1.2.x - 1.6.x.

 Bernhard> hehe, sounds familiar. I've already had my share of fun
 Bernhard> with Ulf in exactly this area and consequently there is
 Bernhard> that git-repo which fixes alot of this stuff for good.

I take it that you have completely stopped committing to svn - Would
you object to me cherry picking a few commits from your git repo
(E.G. newer toolchains)?

-- 
Bye, Peter Korsgaard

[Buildroot] build problems

[Bernhard Fischer]

On Wed, Mar 26, 2008 at 11:39:41PM +0100, Peter Korsgaard wrote:
>>>>>> "Bernhard" == Bernhard Fischer <rep.dot.nop@gmail.com> writes:
>
>Hi,
>
> >> To me it doesn't make sense to keep earlier versions than the latest
> >> stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)
> >> - Otherwise it'll get too hard to handle. I think it's also soon time
> >> to retire some of the really ancient versions like 1.2.x - 1.6.x.
>
> Bernhard> hehe, sounds familiar. I've already had my share of fun
> Bernhard> with Ulf in exactly this area and consequently there is
> Bernhard> that git-repo which fixes alot of this stuff for good.
>
>I take it that you have completely stopped committing to svn - Would
>you object to me cherry picking a few commits from your git repo
>(E.G. newer toolchains)?

The git tree is publically available for anybody to use under the terms
and conditions of the license, so take it or leave it, as a whole or in
parts, sure.

But apart from you guys using outdated toolchains, let me point you to
the more severe issue that you guys (i.e. not my git tree) build with
fux0red up CFLAGS, so you'd better start off with fixing that before
anything else.
I think that i solved this nicely and cleanly in my tree.
I even fixed some of the most annoying breakage (or my inability to use
it properly, depending on your POV) that Ulf applied over time, fwiw.

HTH,
Bernhard

[Buildroot] build problems

[Ulf Samuelsson]

> I see that the directory only has a busybox config for 1.6.1 and
> 1.9.1, so it's broken anyway if the user selects anything else than
> that.

Yes, and then the user is responsible for creating a configuration for that.
The current tree will modify the configuration of an existing .config
file without warning the user, which is even more broken.

> 
> To me it doesn't make sense to keep earlier versions than the latest
> stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)

What you are saying here is that you do not want to allow people
to decide for themselves when they should upgrade the busybox version.
I think a lot of project managers would have an issue with this.

> - Otherwise it'll get too hard to handle. I think it's also soon time
> to retire some of the really ancient versions like 1.2.x - 1.6.x.
> 

Best Regards
Ulf Samuelsson

[Buildroot] build problems

[Peter Korsgaard]

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

 >> I see that the directory only has a busybox config for 1.6.1 and
 >> 1.9.1, so it's broken anyway if the user selects anything else than
 >> that.

 Ulf> Yes, and then the user is responsible for creating a
 Ulf> configuration for that.  The current tree will modify the
 Ulf> configuration of an existing .config file without warning the
 Ulf> user, which is even more broken.

.. Because the hidding magic in the Makefile is broken. The config
option is called BR2_BUSYBOX_VERSION_1_9_X instead of 1_9_1 for a
reason.

 >> 
 >> To me it doesn't make sense to keep earlier versions than the latest
 >> stable release of a given major version (E.G. 1.9.2 instead of 1.9.1)

 Ulf> What you are saying here is that you do not want to allow people
 Ulf> to decide for themselves when they should upgrade the busybox version.
 Ulf> I think a lot of project managers would have an issue with this.

Exactly - Just like all the other packages we have.

Buildroot lives and evolves over time (and it has to). If you want a
static config, just don't change your buildroot snapshot.

-- 
Bye, Peter Korsgaard

[Buildroot] build problems

[Steve Calfee]

Hi John,

I can't speak for Tim. My problems are that stuff I don't know about and don't know how to change - entirely unrelated to embedded kernel issues cause my build to break. I have a newly svn update'd source tree. I would just once like to build a default config before I start customizing. I cannot get through a make. Thats why I keep asking if anyone has a default config (for an arm926) that will build with the current (or any previously tagged) svn tree. I run Ubuntu feisy and think I have all the necessary host tools.

This sequence was copied from the http://www.linux4sam.org/twiki/bin/view/Linux4SAM/BuildRoot website where I do:

$ make menuconfig
$ make at91sam9260dfc_defconfig
$ make > at91sam9260dfc.log 2>&1

and here is a snip of the log file:

cp /home/calfee/buildroot/arm/buildroot/toolchain_build_arm/ccache-2.4/ccache /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin
# Keep the actual toolchain binaries in a directory at the same level.
# Otherwise, relative paths for include dirs break.
mkdir -p /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache
(cd /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache; \
                ln -fs arm-linux-uclibc-gcc arm-linux-gcc; \
                ln -fs arm-linux-uclibc-gcc arm-linux-cc; \
                ln -fs arm-linux-uclibc-gcc arm-linux-uclibc-cc; \
        )
[ -f /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc ] && \
                mv /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc \
                        /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache/
(cd /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin; \
                ln -fs ccache arm-linux-cc; \
                ln -fs ccache arm-linux-gcc; \
                ln -fs ccache arm-linux-uclibc-cc; \
                ln -fs ccache arm-linux-uclibc-gcc; \
        )
[ -f /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-c++ ] && \
                mv /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-c++ \
                        /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache/
[ -f /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-g++ ] && \
                mv /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-g++ \
                        /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache/
(cd /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin; \
                ln -fs ccache arm-linux-c++; \
                ln -fs ccache arm-linux-g++;\
                ln -fs ccache arm-linux-uclibc-c++; \
                ln -fs ccache arm-linux-uclibc-g++; \
        )
(cd /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache; \
                ln -fs arm-linux-uclibc-c++ arm-linux-c++; \
                ln -fs arm-linux-uclibc-g++ arm-linux-g++; \
        )
mkdir -p /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/bin
/usr/bin/gcc -g -O2 .//toolchain/sstrip/sstrip.c -o /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-sstrip
ln -snf ../../bin/arm-linux-uclibc-sstrip \
                /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/bin/sstrip
ln -snf arm-linux-uclibc-sstrip \
                /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-sstrip
/home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc -O2  -I/home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/include -I/home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/include --sysroot=/home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/ -isysroot /home/calfee/buildroot/arm/buildroot/build_arm/staging_dir .//toolchain/sstrip/sstrip.c -o /home/calfee/buildroot/arm/buildroot/project_build_arm/at91sam9260dfc/root/usr/bin/sstrip
/home/calfee/buildroot/arm/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.2.1/../../../../arm-linux-uclibc/bin/ld: cannot open output file /home/calfee/buildroot/arm/buildroot/project_build_arm/at91sam9260dfc/root/usr/bin/sstrip: No such file or directory
collect2: ld returned 1 exit status
make: *** [/home/calfee/buildroot/arm/buildroot/project_build_arm/at91sam9260dfc/root/usr/bin/sstrip] Error 1
[1]+  Exit 2                  make > at91sam9260dfc.log 2>&1

 
 Then I checked to see if sstrip exists:
 
 calfee at squiggy-linux:~/buildroot/arm/buildroot$ find . -name sstrip
./build_arm/staging_dir/usr/arm-linux-uclibc/bin/sstrip
./toolchain/sstrip

calfee at squiggy-linux:~/buildroot/arm/buildroot$ ./build_arm/staging_dir/usr/arm-linux-uclibc/bin/sstrip
Usage: sstrip FILE...
sstrip discards all nonessential bytes from an executable.


And it does, so the path in the makefile must be wrong.

Indeed:
calfee at squiggy-linux:~/buildroot/arm/buildroot$ /home/calfee/buildroot/arm/buildroot/project_build_arm/at91sam9260dfc/root/usr/bin/sstrip
bash: /home/calfee/buildroot/arm/buildroot/project_build_arm/at91sam9260dfc/root/usr/bin/sstrip: No such file or directory

So in this case it seems something has changed in directory naming and somewhere the makefiles are broken. I don't think I have any changed files in my source tree.

As one new to the current buildroot system, I have no idea how to proceed.

Regards, Steve






      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Buildroot] build problems

[Tim Barr]

I have had a similar problem, Steve. I wonder if any of the maintainers
has tried running buildroot after a dirclean recently? Or cleared out
the download directory to see if any package download interfaces have
changed? I have been trying to get a successful buildroot process (for
an AT91SAM9260EK) to complete for over 3 months now with no luck
whatsoever. I ended up having to buy a Timesys linuxlink license in
order to move forward.

Timothy Barr
Hardware Development Engineer
for Multi-Tech Systems, Inc.
tbarr at multitech.com



> -----Original Message-----
> From: buildroot-bounces at uclibc.org 
> [mailto:buildroot-bounces at uclibc.org] On Behalf Of Steve Calfee
> Sent: Sunday, March 23, 2008 10:51 AM
> To: buildroot at uclibc.org
> Subject: Re: [Buildroot] build problems
> 
> 
> Hi All,
> 
> I used buildroot a couple of years ago successfully with a 
> samsung 2410 soc.
> 
> I am now trying to use it for a new project. My problem is I 
> cannot get any build to work.
>  
> Has anyone done a svn update and select a default config and 
> have it build? I want to build an arm system, but first I 
> would like some default config to build. I am using ubuntu 
> feisty and think I have installed all the required tools. The 
> mailing list seems to be quite active, but things seem to be 
> in chaos. Can anyone tell me a starting place that is known to work?
> 
> Thanks, Steve
> 
> 
> 
>       
> ______________________________________________________________
> ______________________
> Be a better friend, newshound, and 
> know-it-all with Yahoo! Mobile.  Try it now.  
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] build problems

[John Voltz]

Timothy,

What type of problems are you having with buildroot? What's failing for you?

John Voltz

On Mon, Mar 24, 2008 at 8:45 AM, Tim Barr <tbarr@multitech.com> wrote:

> I have had a similar problem, Steve. I wonder if any of the maintainers
> has tried running buildroot after a dirclean recently? Or cleared out
> the download directory to see if any package download interfaces have
> changed? I have been trying to get a successful buildroot process (for
> an AT91SAM9260EK) to complete for over 3 months now with no luck
> whatsoever. I ended up having to buy a Timesys linuxlink license in
> order to move forward.
>
> Timothy Barr
> Hardware Development Engineer
> for Multi-Tech Systems, Inc.
> tbarr at multitech.com
>
>
>
> > -----Original Message-----
> > From: buildroot-bounces at uclibc.org
> > [mailto:buildroot-bounces at uclibc.org] On Behalf Of Steve Calfee
> > Sent: Sunday, March 23, 2008 10:51 AM
> > To: buildroot at uclibc.org
> > Subject: Re: [Buildroot] build problems
> >
> >
> > Hi All,
> >
> > I used buildroot a couple of years ago successfully with a
> > samsung 2410 soc.
> >
> > I am now trying to use it for a new project. My problem is I
> > cannot get any build to work.
> >
> > Has anyone done a svn update and select a default config and
> > have it build? I want to build an arm system, but first I
> > would like some default config to build. I am using ubuntu
> > feisty and think I have installed all the required tools. The
> > mailing list seems to be quite active, but things seem to be
> > in chaos. Can anyone tell me a starting place that is known to work?
> >
> > Thanks, Steve
> >
> >
> >
> >
> > ______________________________________________________________
> > ______________________
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile.  Try it now.
> > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot
> >
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080324/3ef03030/attachment.htm 

[Buildroot] build problems

[Lucian Lazarescu]

Hi,
Same problem here. I run ubuntu feisty.
My output:

lucian at lucian-laptop:~/buildroot$ sudo make
target/linux/Makefile.in.advanced:395: warning: overriding commands for
target `/tftpboot/"vmlinux"'
target/linux/Makefile.in.advanced:391: warning: ignoring old commands
for target `/tftpboot/"vmlinux"'

Checking build system dependencies:
Overriding $(DL_DIR) in '.config'.              Ok
External download directory:                    Ok
(/home/lucian/arm/install/downloads)
CC clean:                                       Ok
CXX clean:                                      Ok
CPP clean:                                      Ok
CFLAGS clean:                                   Ok
INCLUDES clean:                                 Ok
CXXFLAGS clean:                                 Ok
which installed:                                Ok
sed works:                                      Ok (/bin/sed)
GNU make version '3.81':                        Ok
C compiler '/usr/bin/gcc'
C compiler version '4.2.3':                     Ok
C++ compiler '/usr/bin/g++'
C++ compiler version '4.2.3':                   Ok
bison installed:                                Ok
flex installed:                                 Ok
gettext installed:                              Ok
makeinfo installed:                             Ok
Build system dependencies:                      Ok

rm
-rf /home/lucian/buildroot/project_build_arm/at91sam9260dfc/buildroot-config
mkdir -p /home/lucian/buildroot/project_build_arm/at91sam9260dfc
cp -dpRf
package/config/buildroot-config /home/lucian/buildroot/project_build_arm/at91sam9260dfc/buildroot-config
mkdir
-p /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc
echo ""
> /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc/issue
echo ""
>> /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc/issue
echo "Welcome to the Erik's uClibc development environment running on
the AT91SAM9260EK"
>> /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc/issue
mkdir
-p /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc
echo "at91sam9260dfc"
> /home/lucian/buildroot/project_build_arm/at91sam9260dfc/root/etc/hostname
PATH="/home/lucian/buildroot/toolchain_build_arm/bin:/home/lucian/buildroot/build_arm/staging_dir/bin:/home/lucian/buildroot/build_arm/staging_dir/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin" /usr/bin/make -j2 -C /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial install-gcc
make[1]: Entering directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial'
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr /home/lucian/buildroot/build_arm/staging_dir/usr
make[2]: Entering directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/fixincludes'
rm
-rf /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/fixincludes/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools 
mkdir -p
-- /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/fixincludes/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/fixincludes/README-fixinc \
          /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include/README
/usr/bin/install -c
fixinc.sh /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/fixinc.sh
/usr/bin/install -c fixincl \
          /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/fixincl
/usr/bin/install -c
mkheaders /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders
make[2]: Leaving directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/fixincludes'
make[2]: Entering directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/gcc'
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/bin
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/include
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/info
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7
for file in cc1  gnat1 cc1plus f951 jc1 jvgenmain cc1obj cc1objplus
tree1; do \
          if [ -f $file ] ; then \
            rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/$file; \
            /usr/bin/install -c
$file /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/$file; \
          else true; \
          fi; \
        done
rm
-rf /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include
mkdir /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include
chmod a
+rx /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include
/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools
/usr/bin/make \
          CFLAGS="-g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Wold-style-definition
-Wmissing-format-attribute  " \
          CONFIG_H="tconfig.h
auto-host.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../include/ansidecl.h" \
          MAKEOVERRIDES= \

mkinstalldirs='/bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs' \
          -f libgcc.mk install
make[3]: Entering directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/gcc'
/usr/bin/install -c -m
644 ./libgcc.a /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/
chmod
644 /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/libgcc.a
/home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ranlib /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/libgcc.a
/usr/bin/install -c -m
644 ./libgcov.a /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/
chmod
644 /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/libgcov.a
/home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ranlib /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/libgcov.a
make[3]: Leaving directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/gcc'
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-cpp
/usr/bin/install -c -m 755
cpp /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-cpp
if [ x != x ]; then \
          rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr//arm-linux-uclibc-cpp; \
          /usr/bin/install -c -m 755
cpp /home/lucian/buildroot/build_arm/staging_dir/usr//arm-linux-uclibc-cpp; \
        else true; fi
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcc.1
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/gcc.1 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcc.1
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcc.1
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-cpp.1
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/cpp.1 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-cpp.1
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-cpp.1
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcov.1
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/gcov.1 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcov.1
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man1/arm-linux-uclibc-gcov.1
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/fsf-funding.7
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/fsf-funding.7 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/fsf-funding.7
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/fsf-funding.7
rm -f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gfdl.7
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/gfdl.7 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gfdl.7
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gfdl.7
rm -f /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gpl.7
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/doc/gpl.7 /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gpl.7
chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/man/man7/gpl.7
rm -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/cpp.info
if [ -f doc/cpp.info ]; then \
          for f in doc/cpp.info*; do \
            realfile=`echo $f | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            /usr/bin/install -c -m 644
$f /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
          done; \
        else true; fi
if /bin/bash -c 'install-info --version' >/dev/null 2>&1; then \
          if
[ -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/cpp.info ];
then \
            install-info
--dir-file=/home/lucian/buildroot/build_arm/staging_dir/usr/info/dir /home/lucian/buildroot/build_arm/staging_dir/usr/info/cpp.info; \
          else true; fi; \
        else true; fi;
for file in   collect2 ..; do \
          if [ x"$file" != x.. ]; then \
            rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/$file; \
            /usr/bin/install -c
$file /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/$file; \
          else true; fi; \
        done
for file in crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o ..; do
\
          if [ x"$file" != x.. ]; then \
            rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/$file; \
            /usr/bin/install -c -m 644
$file /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/$file; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/$file; \
          else true; fi; \
        done
* Cpp: (cpp). The GNU C preprocessor.
install-info(/home/lucian/buildroot/build_arm/staging_dir/usr/info/cpp.info): replacing existing dir entry for `cpp'
rm -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gcc.info
if [ -f doc/gcc.info ]; then \
          for f in doc/gcc.info*; do \
            realfile=`echo $f | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            /usr/bin/install -c -m 644
$f /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
          done; \
        else true; fi
if /bin/bash -c 'install-info --version' >/dev/null 2>&1; then \
          if
[ -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gcc.info ];
then \
            install-info
--dir-file=/home/lucian/buildroot/build_arm/staging_dir/usr/info/dir /home/lucian/buildroot/build_arm/staging_dir/usr/info/gcc.info; \
          else true; fi; \
        else true; fi;
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/specs
if [ -f protoize ]; then \
          rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-protoize; \
          /usr/bin/install -c
protoize /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-protoize; \
          rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-unprotoize; \
          /usr/bin/install -c
unprotoize /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-unprotoize; \
          rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/SYSCALLS.c.X; \
          /usr/bin/install -c -m 644
SYSCALLS.c.X /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/SYSCALLS.c.X; \
          chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/SYSCALLS.c.X; \
        fi
if [ -f gcov ]; \
        then \
            rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcov; \
            /usr/bin/install -c
gcov /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcov; \
        fi
* gcc: (gcc). The GNU Compiler Collection.
install-info(/home/lucian/buildroot/build_arm/staging_dir/usr/info/gcc.info): replacing existing dir entry for `gcc'
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/info/cppinternals.info
if [ -f doc/cppinternals.info ]; then \
          for f in doc/cppinternals.info*; do \
            realfile=`echo $f | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            /usr/bin/install -c -m 644
$f /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
          done; \
        else true; fi
if /bin/bash -c 'install-info --version' >/dev/null 2>&1; then \
          if
[ -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/cppinternals.info ]; then \
            install-info
--dir-file=/home/lucian/buildroot/build_arm/staging_dir/usr/info/dir /home/lucian/buildroot/build_arm/staging_dir/usr/info/cppinternals.info; \
          else true; fi; \
        else true; fi;
/usr/bin/install -c
gccbug /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gccbug
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccinstall.info
* Cpplib: (cppinternals). Cpplib internals.
if [ -f doc/gccinstall.info ]; then \
          for f in doc/gccinstall.info*; do \
            realfile=`echo $f | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            /usr/bin/install -c -m 644
$f /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
          done; \
        else true; fi
install-info(/home/lucian/buildroot/build_arm/staging_dir/usr/info/cppinternals.info): replacing existing dir entry for `cppinternals'
rm -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccint.info
if /bin/bash -c 'install-info --version' >/dev/null 2>&1; then \
          if
[ -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccinstall.info ]; then \
            install-info
--dir-file=/home/lucian/buildroot/build_arm/staging_dir/usr/info/dir /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccinstall.info; \
          else true; fi; \
        else true; fi;
if [ -f doc/gccint.info ]; then \
          for f in doc/gccint.info*; do \
            realfile=`echo $f | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            /usr/bin/install -c -m 644
$f /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
            chmod
a-x /home/lucian/buildroot/build_arm/staging_dir/usr/info/$realfile; \
          done; \
        else true; fi
* gccinstall: (gccinstall). Installing the GNU Compiler Collection.
install-info(/home/lucian/buildroot/build_arm/staging_dir/usr/info/gccinstall.info): replacing existing dir entry for `gccinstall'
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc
/usr/bin/install -c
xgcc /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc
if /bin/bash -c 'install-info --version' >/dev/null 2>&1; then \
          if
[ -f /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccint.info ]; then \
            install-info
--dir-file=/home/lucian/buildroot/build_arm/staging_dir/usr/info/dir /home/lucian/buildroot/build_arm/staging_dir/usr/info/gccint.info; \
          else true; fi; \
        else true; fi;
rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc-4.2.1
( cd /home/lucian/buildroot/build_arm/staging_dir/usr/bin && \
           ln arm-linux-uclibc-gcc arm-linux-uclibc-gcc-4.2.1 )
* gccint: (gccint). Internals of the GNU Compiler Collection.
install-info(/home/lucian/buildroot/build_arm/staging_dir/usr/info/gccint.info): replacing existing dir entry for `gccint'
if [ -f gcc-cross ] ; then \
          if
[ -d /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/../../../../arm-linux-uclibc/bin/. ] ; then \
            rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/../../../../arm-linux-uclibc/bin/gcc; \
            /usr/bin/install -c
gcc-cross /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/../../../../arm-linux-uclibc/bin/gcc; \
          else true; fi; \
        else \
          rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc-tmp; \
          ( cd /home/lucian/buildroot/build_arm/staging_dir/usr/bin && \
            ln arm-linux-uclibc-gcc arm-linux-uclibc-gcc-tmp && \
            mv -f arm-linux-uclibc-gcc-tmp
arm-linux-uclibc-arm-linux-uclibc-gcc ); \
        fi
(cd `${PWDCMD-pwd}`/include ; \
         tar -cf - .; exit 0) |
(cd /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include; tar xpf - )
for file
in /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/decfloat.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/float.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/iso646.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/stdarg.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/stdbool.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/stddef.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/ginclude/varargs.h /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/config/arm/mmintrin.h; do \
          realfile=`echo $file | sed -e 's|.*/\([^/]*\)$|\1|'`; \
          /usr/bin/install -c -m 644 $file \
            /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include/$realfile ; \
        done
/usr/bin/install -c -m 644
xlimits.h /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include/limits.h
files=`cd /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include; find . -type l -print 2>/dev/null`; \
        if [ $? -eq 0 ]; then \
          dir=`cd include; ${PWDCMD-pwd}`; \
          for i in $files; do \
            dest=`ls
-ld /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include/$i | sed -n 's/.*-> //p'`; \
            if expr "$dest" : "$dir.*" > /dev/null; then \
              rm
-f /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include/$i; \
              ln -s `echo $i | sed "s|/[^/]*|/..|g" | sed
's|/..$||'``echo "$dest" | sed "s|
$dir||"` /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/include/$i; \
            fi; \
          done; \
        fi
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/unwind-generic.h /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/include/unwind.h
/usr/bin/install -c -m
644 /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/gsyslimits.h \
          /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/gsyslimits.h
/usr/bin/install -c -m 644
macro_list /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/macro_list
if [ x != x ] ; then \
          /usr/bin/install
-c /bin/bash /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/../mkinstalldirs \
                /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/mkinstalldirs ; \
          /usr/bin/install
-c /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1/gcc/fixproto /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/fixproto ; \
          /usr/bin/install -c build/fix-header \
                /home/lucian/buildroot/build_arm/staging_dir/usr/libexec/gcc/arm-linux-uclibc/4.2.1/install-tools/fix-header ; \
        else :; fi
echo
'SYSTEM_HEADER_DIR="'"`echo /home/lucian/buildroot/toolchain_build_arm/uClibc_dev//usr/include | sed -e :a -e 's,[^/]*/\.\.\/,,' -e ta`"'"' \

> /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders.conf
echo 'OTHER_FIXINCLUDES_DIRS=""' \

>> /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders.conf
echo 'FIXPROTO_DEFINES=""' \

>> /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders.conf
echo 'STMP_FIXPROTO=""' \

>> /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders.conf
echo 'STMP_FIXINC="stmp-fixinc"' \

>> /home/lucian/buildroot/build_arm/staging_dir/usr/lib/gcc/arm-linux-uclibc/4.2.1/install-tools/mkheaders.conf
make[2]: Leaving directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/gcc'
make[1]: Leaving directory
`/home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial'
touch /home/lucian/buildroot/toolchain_build_arm/gcc-4.2.1-initial/.installed
/usr/bin/make MAKE="/usr/bin/make -j1"
-C /home/lucian/buildroot/toolchain_build_arm/uClibc-0.9.29 \
                PREFIX= \
                DEVEL_PREFIX=/ \
                RUNTIME_PREFIX=/ \
                HOSTCC="/usr/bin/gcc" \
                all
make[1]: Entering directory
`/home/lucian/buildroot/toolchain_build_arm/uClibc-0.9.29'
make[2]: `conf' is up to date.
  CC ldso/ldso/ldso.oS
cc1: error: unrecognized command line option "-mfdpic"
make[1]: *** [ldso/ldso/ldso.oS] Error 1
make[1]: Leaving directory
`/home/lucian/buildroot/toolchain_build_arm/uClibc-0.9.29'
make: ***
[/home/lucian/buildroot/toolchain_build_arm/uClibc-0.9.29/lib/libc.a]
Error 2
lucian at lucian-laptop:~/buildroot$ 

Best regards,
Lucian.


On Mon, 2008-03-24 at 07:45 -0500, Tim Barr wrote:
> I have had a similar problem, Steve. I wonder if any of the maintainers
> has tried running buildroot after a dirclean recently? Or cleared out
> the download directory to see if any package download interfaces have
> changed? I have been trying to get a successful buildroot process (for
> an AT91SAM9260EK) to complete for over 3 months now with no luck
> whatsoever. I ended up having to buy a Timesys linuxlink license in
> order to move forward.
> 
> Timothy Barr
> Hardware Development Engineer
> for Multi-Tech Systems, Inc.
> tbarr at multitech.com
> 
> 
> 
> > -----Original Message-----
> > From: buildroot-bounces at uclibc.org 
> > [mailto:buildroot-bounces at uclibc.org] On Behalf Of Steve Calfee
> > Sent: Sunday, March 23, 2008 10:51 AM
> > To: buildroot at uclibc.org
> > Subject: Re: [Buildroot] build problems
> > 
> > 
> > Hi All,
> > 
> > I used buildroot a couple of years ago successfully with a 
> > samsung 2410 soc.
> > 
> > I am now trying to use it for a new project. My problem is I 
> > cannot get any build to work.
> >  
> > Has anyone done a svn update and select a default config and 
> > have it build? I want to build an arm system, but first I 
> > would like some default config to build. I am using ubuntu 
> > feisty and think I have installed all the required tools. The 
> > mailing list seems to be quite active, but things seem to be 
> > in chaos. Can anyone tell me a starting place that is known to work?
> > 
> > Thanks, Steve
> > 
> > 
> > 
> >       
> > ______________________________________________________________
> > ______________________
> > Be a better friend, newshound, and 
> > know-it-all with Yahoo! Mobile.  Try it now.  
> > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org http://busybox.net/mailman/listinfo/buildroot
> > 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot

[Buildroot] build problems

[Ulf Samuelsson]

>I have had a similar problem, Steve. I wonder if any of the maintainers
> has tried running buildroot after a dirclean recently? Or cleared out
> the download directory to see if any package download interfaces have
> changed? I have been trying to get a successful buildroot process (for
> an AT91SAM9260EK) to complete for over 3 months now with no luck
> whatsoever. I ended up having to buy a Timesys linuxlink license in
> order to move forward.
> 
> Timothy Barr
> Hardware Development Engineer
> for Multi-Tech Systems, Inc.
> tbarr at multitech.com
> 

I build  at91sam9260dfc_defconfig regularily on my 
OpenSuSE 10.2 system and it seems to compile OK.
If you add more packages using menuconfig, there could be
problems of course.



Best Regards
Ulf Samuelsson 

[Buildroot] build problems

[Steve Calfee]

Hi All,

I used buildroot a couple of years ago successfully with a samsung 2410 soc.

I am now trying to use it for a new project. My problem is I cannot get any build to work.
 
Has anyone done a svn update and select a default config and have it build? I want to build an arm system, but first I would like some default config to build. I am using ubuntu feisty and think I have installed all the required tools. The mailing list seems to be quite active, but things seem to be in chaos. Can anyone tell me a starting place that is known to work?

Thanks, Steve



      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Buildroot] build problems

[Ulf Samuelsson]

> Hi All,
> 
> I used buildroot a couple of years ago successfully with a samsung 2410 soc.
> 
> I am now trying to use it for a new project. My problem is I cannot get any build to work.
> 
> Has anyone done a svn update and select a default config and have it build? I want to build an arm system, but first I would like some default config to build. I am using ubuntu feisty and think I have installed all the required tools. The mailing list seems to be quite active, but things seem to be in chaos. Can anyone tell me a starting place that is known to work?
> 
> Thanks, Steve
> 
There is no support for SAMSUNG 2410, which in practice means
that you have to disable building linux/U-boot etc, and only build the root fs.


Best Regards
Ulf Samuelsson

[Buildroot] build problems

[Steve Calfee]

Hi, I am continually having problems building.
I have the latest svn sources.

Does anybody know which of the arm926 projects ie xxxx_defconfig currently is buildable. I would like to get an existing build to work before I customize it. I am running on ubuntu Feisty.

As a second question, if I wish to change the package selection, do I need to do a make clean? or will another make only deal with the current package selections? If I do a make menuconfig, does it blitz the existing .config back to defaults, or can I change packages at will starting with whatever prebuilt xxx-defconfig I used?

Thanks, Steve









      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ