Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: glscantlen <glscantlen@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] build libstdc++.so.6
Date: Thu, 23 Jul 2015 09:25:44 -0700 (PDT)	[thread overview]
Message-ID: <1437668744769-107004.post@n4.nabble.com> (raw)
In-Reply-To: <20150723085718.745044df@free-electrons.com>

Thanks for these suggestions. It's all good and useful. Too much to address
all at once. I will attack them one at a time and try to keep this thread
updated with my progress. I agree with your summary and the final build
process should be as clean and simple as possible. That is my goal too.

For the "instructions" my intent was to show the reader how I arrived at the
"simple clean build process". It is more of an instruction on how to create
the build not just instructions on how to execute the build. So for
addressing points like #7, I would keep these instructions. They are
procedures for creating "odroidxu3_mplayer_defconfig". You could argue there
are better ways to present the procedures but that may be of some personal
preference.

Thanks again for your expertise and assistance.
If you prefer that I start a new thread or continue this discussion
else-where I can accommodate.




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/build-libstdc-so-6-with-custom-toolchain-Linaro-4-9-tp105322p107004.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

      reply	other threads:[~2015-07-23 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 17:03 [Buildroot] build libstdc++.so.6 glscantlen
2015-07-11 22:28 ` Thomas Petazzoni
2015-07-22 16:56   ` glscantlen
2015-07-22 20:00     ` Thomas Petazzoni
2015-07-22 23:34       ` glscantlen
2015-07-23  6:57         ` Thomas Petazzoni
2015-07-23 16:25           ` glscantlen [this message]

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=1437668744769-107004.post@n4.nabble.com \
    --to=glscantlen@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