From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] aiccu: new package
Date: Wed, 11 Sep 2013 08:07:14 +0200 [thread overview]
Message-ID: <52300892.2030700@mind.be> (raw)
In-Reply-To: <CAAXf6LXxcmwVN3hoaV0YqNyN5HPYQSkmqtJ4RBwYYOmQJTLUfA@mail.gmail.com>
On 08/09/13 13:39, Thomas De Schampheleire wrote:
> I tried compiling on a powerpc target, but this unfortunately failed:
>
> strip aiccu
> strip: Unable to recognise the format of the input file `aiccu'
> make[2]: *** [aiccu] Error 1
> make[2]: Leaving directory
> `/home/tdescham/repo/contrib/buildroot-review/output/build/aiccu-20070115/unix-console'
>
>
> The aiccu/unix-console/Makefile hardcodes the 'strip' command, but
> this should be the cross-strip, provided by buildroot through
> TARGET_STRIP. I think that aiccu should be patched to use STRIP, which
> defaults to 'strip', and aiccu.mk in buildroot should then pass the
> right STRIP command.
> This patch could then also be upstreamed...
Actually, it is better to remove the strip completely. We strip the
target directory in a final step, so that you still have unstripped
binaries in the build and staging directories. Most packages leave it up
to the distro to strip the binaries - which makes it possible to build
foo-dbg packages that have the debug symbols.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-09-11 6:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 21:56 [Buildroot] [PATCH 1/1] aiccu: new package Michael Rommel
2013-09-07 20:56 ` Thomas De Schampheleire
2013-09-08 11:39 ` Thomas De Schampheleire
2013-09-11 6:07 ` Arnout Vandecappelle [this message]
[not found] ` <150C0AB5-B4C6-4379-9FEE-9819278AAF69@layer-7.net>
[not found] ` <CAAXf6LWetaF-1wTWvhad-gKFc0CwLrqTKjgM_F9Seou+Pm=UWg@mail.gmail.com>
2013-09-08 15:28 ` Michael Rommel
2013-09-08 17:46 ` Thomas De Schampheleire
2013-09-08 18:28 ` Michael Rommel
2013-09-09 8:41 ` Thomas De Schampheleire
-- strict thread matches above, loose matches on Subject: below --
2013-09-08 21:58 Michael Rommel
2013-09-11 18:34 ` Michael Rommel
2013-09-11 19:52 ` Thomas De Schampheleire
2013-09-11 21:22 ` Arnout Vandecappelle
2013-09-02 23:49 Michael Rommel
2013-09-04 16:38 ` Arnout Vandecappelle
2013-09-04 20:50 ` Michael Rommel
2013-09-05 8:13 ` Thomas Petazzoni
2013-09-05 22:03 ` Michael Rommel
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=52300892.2030700@mind.be \
--to=arnout@mind.be \
--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