From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Holger Freyther <holger@freyther.de>
Cc: poky@yoctoproject.org
Subject: Re: Odd log messages for apps using autotools and __FILE__
Date: Sat, 08 Aug 2015 09:30:43 -0700 [thread overview]
Message-ID: <1439051443.30467.56.camel@linuxfoundation.org> (raw)
In-Reply-To: <5331BB7A-0C6A-42AE-BA46-4E7A9D970FB4@freyther.de>
On Fri, 2015-08-07 at 20:26 +0200, Holger Freyther wrote:
> Hi,
>
> in the Osmocom software and rauc and probably many applications that use __FILE__ in a
> log statement the log output is now:
>
> /home/hfreyther/images/poky/build/tmp/work/sysmobts_v2-poky-linux-gnueabi/rauc/0+gitAUTOINC+d44adb0079-r4/git/src/install.c:811 I will unmount /mnt/rauc/rootfs.0
>
> where it used to be:
>
> install.c:811 I will unmount /mnt/rauc/rootfs.0
>
>
> I know I can use __BASE_FILE__ in gcc to get back to install.c but I wonder where this is
> coming from? Is this a side-effect of using B!=S? Is there another config that was made to
> pass the full path to the compiler?
I can confirm that this is from the B != S change.
We've kept meaning to go and look at how gcc generates these paths to
maybe try and add the option to remove a prefix for example. The .debug
src paths have a rewrite mechanism and we could use this for other paths
too?
Cheers,
Richard
next prev parent reply other threads:[~2015-08-08 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 18:26 Odd log messages for apps using autotools and __FILE__ Holger Freyther
2015-08-08 16:30 ` Richard Purdie [this message]
2015-08-08 18:09 ` Holger Freyther
2015-08-08 19:19 ` Khem Raj
2015-08-10 7:04 ` Holger Freyther
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=1439051443.30467.56.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=holger@freyther.de \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.