Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain and sysroot
Date: Thu, 25 Mar 2010 18:08:49 +0000 (UTC)	[thread overview]
Message-ID: <hog8rg$sis$1@dough.gmane.org> (raw)
In-Reply-To: 44830928.20100325201616@ya.ru

On 2010-03-25, Yury Luneff <bitterman@ya.ru> wrote:
> i've fixed uemacs makefile.
>
> And the other problem was not with openvpn but with vsftpd which .mk did 
> not include "${TARGET_LDFLAGS}" at all.
>
> It seem to be a common problem in buildroot for now.

Based on my sample of three packages (two had the problem), I'm
guessing it's a very common problem.  It looks like the buildroot
developers use external toolchains that don't require a --sysroot
option.  I don't know why that is, since external toolchains get
copied into staging before they are used.  That implies that they
won't work without a --sysroot option...

-- 
Grant Edwards               grant.b.edwards        Yow! My polyvinyl cowboy
                                  at               wallet was made in Hong
                              gmail.com            Kong by Montgomery Clift!

  reply	other threads:[~2010-03-25 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 15:28 [Buildroot] external toolchain and sysroot Yury Luneff
2010-03-25 16:14 ` Grant Edwards
2010-03-25 17:12   ` Yury Luneff
2010-03-25 17:16     ` Yury Luneff
2010-03-25 18:08       ` Grant Edwards [this message]
2010-03-25 22:34         ` Thomas Petazzoni
2010-03-26  1:04           ` Grant Edwards
2010-03-26 19:24             ` Thomas Petazzoni
2010-03-27  1:10               ` Grant Edwards
2010-03-27  8:22                 ` Thomas Petazzoni
2010-03-27 15:05                   ` Grant Edwards
2010-04-14 13:42           ` Grant Edwards
2010-03-25 22:32   ` Thomas Petazzoni

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='hog8rg$sis$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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