From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] python-pyasn: new package
Date: Thu, 3 Oct 2013 23:17:55 +0200 [thread overview]
Message-ID: <20131003231755.72ecace9@skate> (raw)
In-Reply-To: <1380830465-16083-2-git-send-email-rjbarnet@rockwellcollins.com>
Dear Ryan Barnett,
On Thu, 3 Oct 2013 15:01:01 -0500, Ryan Barnett wrote:
> + CFLAGS="$(TARGET_CFLAGS) -I$(STAGING_DIR)/usr/include" \
> + CXX="$(TARGET_CXX)" \
> + CXXFLAGS="$(TARGET_CXXFLAGS) -I$(STAGING_DIR)/usr/include" \
> + LDSHARED="$(TARGET_CC) -shared" \
> + LDFLAGS="$(TARGET_LDFLAGS) -L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib" \
These additional -I and -L are rather weird because they simply pass
what are already the default search paths for headers and libraries.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-03 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 20:01 [Buildroot] [PATCH 0/5] Introduce New Package PySnmp Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 1/5] python-pyasn: new package Ryan Barnett
2013-10-03 21:17 ` Thomas Petazzoni [this message]
2013-10-03 22:39 ` Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 2/5] python-pycrypto: " Ryan Barnett
2013-10-03 20:24 ` Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 3/5] python-pysnmp: " Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 4/5] python-pysnmp-apps: " Ryan Barnett
2013-10-03 20:01 ` [Buildroot] [PATCH 5/5] python-pysnmp-mibs: " Ryan Barnett
2013-10-03 21:15 ` [Buildroot] [PATCH 0/5] Introduce New Package PySnmp Thomas Petazzoni
2013-10-03 21:21 ` Ryan Barnett
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 1:12 Ryan Barnett
2013-10-04 1:12 ` [Buildroot] [PATCH 1/5] python-pyasn: new package Ryan Barnett
2013-10-04 2:27 ` Danomi Manchego
2013-10-04 14:09 ` Ryan Barnett
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=20131003231755.72ecace9@skate \
--to=thomas.petazzoni@free-electrons.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