From: Darcy L. Watkins <dwatkins@tranzeo.com>
To: buildroot@busybox.net
Subject: [Buildroot] [May15 patch 12/12] netsnmp: disable build with external toolchain
Date: Wed, 23 Jun 2010 08:30:31 -0700 [thread overview]
Message-ID: <1277307031.18561.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1277216184.23331.8.camel@localhost.localdomain>
Hello,
The fourth chunk in the buildroot-libtool.patch appears to be bogus. It
adds a commented out chunk of code, but doesn't remove what appears to
have been intended to be the code to comment out (around line # 29xx in
ltmain.sh). It would seem that an "exit 1" was replaced with "exit
$EXIT_FAILURE" so the patch broke. I think it's possible that the patch
was refreshed without anyone catching this.
I also notice what appears to be two different variants of ltmain.sh
floating around in the packages - one circa 2007 (ver 1.5.24), the other
circa 2008 (ver 2.2.6). Only the former is compatible with the patch.
The ltmain.sh in the netsnmp package is the newer one (not compatible
with the patch). Do we need a variant of buildroot-libtool.patch for
the newer libtool, or is the newer ltmain.sh variant supposed to have
the cross compile problems fixed?
Regards,
Darcy
On Tue, 2010-06-22 at 07:16 -0700, Darcy L. Watkins wrote:
> I need to be able to build net-snmp in my buildroot using a
> crosstool-ng
> external toolchain.
>
> Has anyone made progress or determined the underlying cause of why
> net-snmp cannot properly locate the libraries even though --sysroot
> points to the buildroot staging area (instead of using the toolchain
> default)?
>
> Would adding redundant -L<path> to the staging library area work (and
> likely also -I<path> to the includes if needed)?
>
> Any insight as to why this happens with net-snmp (or is it observed
> with
> some other packages too)?
next prev parent reply other threads:[~2010-06-23 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 14:16 [Buildroot] [May15 patch 12/12] netsnmp: disable build with external toolchain Darcy L. Watkins
2010-06-23 15:30 ` Darcy L. Watkins [this message]
2010-06-23 18:25 ` Darcy L. Watkins
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=1277307031.18561.19.camel@localhost.localdomain \
--to=dwatkins@tranzeo.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