Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] for target toolchain to be compiled
Date: Mon, 09 Nov 2009 22:41:40 +0100	[thread overview]
Message-ID: <87d43rs7e3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAHWPmCJoh6pNraKNfwnUAkLCgAAAEAAAAB/2nbG5LTJMskyNbh63LRwBAAAAAA==@cimeq.qc.ca> (Jonathan dumaresq's message of "Mon\, 9 Nov 2009 16\:17\:36 -0500")

>>>>> "Jonathan" == Jonathan dumaresq <jdumaresq@cimeq.qc.ca> writes:

 Jonathan> Hi Peter,
 Jonathan> See the log file attached

 Jonathan>   HOSTCC extra/scripts/unifdef
 Jonathan> extra/scripts/unifdef.c:209: error: conflicting types for 'getline'
 Jonathan> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here

Ok, so that's the problem with unifdef defining a getline function which
conflicts with a function in the C library in never versions of glibc
with the same name.

You need to ensure that the
toolchain/uClibc/uClibc-0.9.30.1-unifdef-getline.patch gets applied to
your toolchain build - presumably by moving it to
toolchain/uClibc/ext_source/Atmel/avr32/0.9.30-avr32-2.1.5 and renaming
it to uClibc-0.9.30-avr32-2.1.5-unifdef-getline.patch

Let me know if that works for you, then I'll fix it in git.
-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-11-09 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 20:52 [Buildroot] for target toolchain to be compiled Jonathan dumaresq
2009-11-09 21:02 ` Peter Korsgaard
2009-11-09 21:17   ` Jonathan dumaresq
2009-11-09 21:41     ` Peter Korsgaard [this message]
2009-11-09 21:46       ` Jonathan dumaresq

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=87d43rs7e3.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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