Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 4.1.2 toolchain build issues [was	svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...]
Date: Tue, 16 Oct 2007 07:15:23 +0200	[thread overview]
Message-ID: <1192511723.28237.2.camel@localhost.localdomain> (raw)
In-Reply-To: <d6cda7730710151846n722419d9t806cea6018d1b54d@mail.gmail.com>

On Tue, 2007-10-16 at 02:46 +0100, Thiago A. Corr?a wrote:
> Ok.... got it to build... it happens to be that atngw100_defconfig now
> builds to a dir without nofp sufix, which makes me wonder if ppl have
> decided weather this thing has or doesn't has an FP, perhaps it's a
> paradox, or a dogma. You just have to belive it works. *smile*
> 

It does not have an FPU, probably just a bad defconfig.

> Anyway, disabled libdaemon, which I never use anyway, and now I get
> the uboot issue as well.... but at least I can work now. It should be
> easily enough to pull uboot from the Atmel AVR32 fork and figure out
> what's wrong. Dealing with packages is so much easier.
> 

The AVR32 fork has the bootloader in target/bootloader/u-boot, and is
quite different from the one in the Atmel directory.

> Btw, is there a reason why u-boot is buried into Atmel folder?
> Shouldn't other archs/chips use it as well?
> 

The AVR32 fork on atmel.no tries to do the bootloader general for all
archs.

> Hopefully I will come back with patches once more (have a better
> qtopia building, in a single stage, on the works).
> 

You can't, Qtopia hard codes the path to the libraries inside the
libraries. I have tried and ended up having to do a two stage build. One
for staging_dir and one for the target dir.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

  reply	other threads:[~2007-10-16  5:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 14:20 [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit: trunk/buildroot: target/device target/device/Atmel target etc...] Thiago A. Corrêa
2007-10-15 21:25 ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svn commit:trunk/buildroot: " Ulf Samuelsson
2007-10-15 22:17   ` don
2007-10-15 22:22     ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...] Ulf Samuelsson
2007-10-15 23:49       ` don
2007-10-16  1:46         ` Thiago A. Corrêa
2007-10-16  5:15           ` Hans-Christian Egtvedt [this message]
2007-10-16  5:57             ` [Buildroot] AVR32 4.1.2 toolchain build issues[was svncommit:trunk/buildroot: target/devicetarget/device/Atmel targetetc...] Ulf Samuelsson
2007-10-16 11:32             ` [Buildroot] AVR32 4.1.2 toolchain build issues [was svncommit:trunk/buildroot: target/device target/device/Atmel targetetc...] Thiago A. Corrêa
2007-10-16 11:46               ` Hans-Christian Egtvedt
2007-10-16 13:10                 ` Thomas Lundquist
2007-10-16  5:36           ` Ulf Samuelsson
2007-10-16  5:27         ` [Buildroot] AVR32 4.1.2 toolchain build issues [wassvncommit:trunk/buildroot: target/device target/device/Atmeltargetetc...] Ulf Samuelsson

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=1192511723.28237.2.camel@localhost.localdomain \
    --to=hcegtvedt@atmel.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