Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Luneff <bitterman@ya.ru>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain and sysroot
Date: Thu, 25 Mar 2010 20:12:40 +0300	[thread overview]
Message-ID: <93399903.20100325201240@ya.ru> (raw)
In-Reply-To: <hog24r$1nu$1@dough.gmane.org>

> In the busybox .mk file, I found that TARGET_LDFLAGS wasn't being used
> (it wasn't being passed to the "make" command).  I had to patch the
> .mk file to pass the TARGET_LDFLAGS value to make.

>> It is definetely not the problem of package as openvpn doesn't find 
>> openssl too and the corresponding .so files are in staging. Or it is 
>> a bug in both uemacs and openvpn which is unprobable.

as for uemacs, its link command disregarded even CFLAGS, so I had to 
patch the makefile of uemacs. So I did the uemacs (just for fun, 
really, it's old like heaven and hell :-). Same problem, I guess. 
Shouldn't it be fixed project-wide? Documentations says that CT-NG is 
ok, but reality says something different.

As for openvpn, I guess the precise commands are common for autotools 
packages, so it is not quite so easy to find the right place to 
strike.

> It sounds like the .mk files are missing something.  See the following
> bugs for patches that show how I fixed missing --sysroot problems for
> busybox and mtd-utils:

Busybox is ok :(

  reply	other threads:[~2010-03-25 17:12 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 [this message]
2010-03-25 17:16     ` Yury Luneff
2010-03-25 18:08       ` Grant Edwards
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=93399903.20100325201240@ya.ru \
    --to=bitterman@ya.ru \
    --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