From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 4/4] toolchain: instrument external toolchain wrapper
Date: Fri, 19 Jul 2013 23:39:45 +0200 [thread overview]
Message-ID: <20130719213945.GE3751@free.fr> (raw)
In-Reply-To: <877ggmutjc.fsf@dell.be.48ers.dk>
On 2013-07-19 23:30 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> >> You could argue that this feature isn't really needed as you can just
> >> run 'strace -s 1000 -e execve <wrapper>' for basically the same
> >> information, but OK - This is perhaps a bit more user friendly.
>
> Yann> My use-case was to see how the kernel build-system was calling the
> Yann> wrapper. So I just ran:
> Yann> BR_DEBUG_WRAPPER=1 make
> Yann> in my Buildroot build dir.
>
> So you are only interested in the arguments to the wrapper, or do you
> want to see the final arguments to the real compiler?
No, I'm interested in the final, complete argv[*].
> >> With that in mind, I think a more sensible output format is something
> >> you can directly cut'n'paste and execute in the shell (after perhaps
> >> tweaking something), so I've changed it to simply print the args space
> >> seperated like this:
>
> Yann> Yet, one of the motivation behind the \n-separated args was to easily
> Yann> see the args, without having to 'parse' the command line with the eyes.
>
> Yann> The Linux kernel is passing something like 40+ args to the wrapper, so
> Yann> the line is getting rather long, and difficult to grok visually, while
> Yann> the one-arg per line output made it very easy.
>
> Ok, but a kernel build with 40+ lines per gcc invocation is presumably
> also quite overwhelming?
The trick is to wait it break, and re-run with BR_DEBUG_WRAPPER=1 set and
then inspect the reason for the breakage.
> Yann> I already owed you one ${BEVERAGE} in Edimburgh; you can make
> Yann> that two, now! ;-)
>
> heh, sounds good ;)
Remember: for each ${BEVERAGE} I owe you, I get one too! :-)
/me is looking forward to it!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2013-07-19 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 21:24 [Buildroot] [pull request] Pull request for branch yem-misc-updates Yann E. MORIN
2013-07-18 21:24 ` [Buildroot] [PATCH 1/4] defconfig/rpi: bump kernel for misc fixes Yann E. MORIN
2013-07-18 22:33 ` Peter Korsgaard
2013-07-18 21:24 ` [Buildroot] [PATCH 2/4] package/nss-mdns: fix avahi socket location Yann E. MORIN
2013-07-18 22:34 ` Peter Korsgaard
2013-07-18 21:24 ` [Buildroot] [PATCH 3/4] package/nss-mdns: do not overwrite user's nsswitch.conf Yann E. MORIN
2013-07-18 22:39 ` Peter Korsgaard
2013-07-18 21:24 ` [Buildroot] [PATCH 4/4] toolchain: instrument external toolchain wrapper Yann E. MORIN
2013-07-18 21:32 ` Thomas Petazzoni
2013-07-18 21:39 ` Yann E. MORIN
2013-07-18 21:54 ` [Buildroot] [PATCHv2 " Yann E. MORIN
2013-07-19 6:33 ` Peter Korsgaard
2013-07-19 16:13 ` Yann E. MORIN
2013-07-19 21:30 ` Peter Korsgaard
2013-07-19 21:39 ` Yann E. MORIN [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=20130719213945.GE3751@free.fr \
--to=yann.morin.1998@free.fr \
--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