Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Fwd: Re: Struggling with undefined reference	to	`__fgetc_unlocked']
Date: Mon, 27 Aug 2007 12:37:56 +0200	[thread overview]
Message-ID: <1188211076.7840.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20070823201759.GO11697@aon.at>


On Thu, 2007-08-23 at 22:18 +0200, Bernhard Fischer wrote:
> On Thu, Aug 23, 2007 at 06:25:59PM +0100, Thiago A. Corr?a wrote:
> >Thanks for the help. It was indeed using the uClibc includes with the
> >CXXFLAGS/CFLAGS being set at the qtopia4.mk. I will send a patch as
> >soon as I confirm this is working. But at least so far compilation got
> >past rcc.
> 
> There was talks about qtopia before. IIRC there is no need to compile it
> for the host in the first place.

Correct, only a two-stage build for the target is necessary. But Qtopia
compiles some tools with the host compiler (qmake, moc, rcc and uic). 

Before the late fixes in Qtopia in Buildroot, some bad CFLAGS and
CXXFLAGS was set when configuring, causing the Qtopia build system to
use wrong headers (i.e. target headers when compiling the host tools).

AFAIK everything should be in order in latest SVN.

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

  reply	other threads:[~2007-08-27 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 16:43 [Buildroot] [Fwd: Re: Struggling with undefined reference to `__fgetc_unlocked'] Carmelo AMOROSO
2007-08-23 16:53 ` Thiago A. Corrêa
2007-08-23 16:57   ` Carmelo AMOROSO
2007-08-23 17:25     ` Thiago A. Corrêa
2007-08-23 20:18       ` Bernhard Fischer
2007-08-27 10:37         ` Hans-Christian Egtvedt [this message]
2007-08-27 13:33           ` Thiago A. Corrêa
2007-08-27 13:48             ` Hans-Christian Egtvedt
2007-08-27 15:50               ` Thiago A. Corrêa

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=1188211076.7840.5.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