Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some issues I have found in buildroot today.
Date: Mon, 12 Jan 2009 16:39:20 +0100	[thread overview]
Message-ID: <87eiz8h6tz.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <C13DBBE85AD6974B85C118C35890CA5F1A85066FB6@EU1RDCRDC1WX029.exi.nxp.com> (Daniel James Laird's message of "Mon\, 12 Jan 2009 16\:34\:13 +0100")

>>>>> "Daniel" == Daniel James Laird <daniel.j.laird@nxp.com> writes:

Hi,

 Daniel> I have found that libcurl is not properly dependent on
 Daniel> host-sed so if I build this package alone it does not work.

And it needs it internally for the build?

 Daniel> I have also found that autoconf can not be built with multi
 Daniel> jobs (i.e -j X).

Ok, that should be fixable with a simple s/MAKE/MAKE1/

 Daniel> I have also found that for external toolchains you cannot set
 Daniel> that you have LOCALE/WCHAR support this limits options
 Daniel> somewhat and means libiconv is always built and I would
 Daniel> rather not do this.  Can anyone explain the LOCALE support
 Daniel> options and what it means for an external toolchain instead
 Daniel> of a uclibc built toolchain.

I guess the LOCALE stuff for external toolchain should just match what
the toolchain has, but I don't use the external stuff.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-12 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 15:22 [Buildroot] svn commit: trunk/buildroot/package/cairo thomasez at uclibc.org
2009-01-12 15:34 ` [Buildroot] Some issues I have found in buildroot today Daniel James Laird
2009-01-12 15:39   ` Peter Korsgaard [this message]
2009-01-12 16:30     ` Daniel James Laird
2009-01-12 16:36       ` Peter Korsgaard

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=87eiz8h6tz.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