From: Sam Ravnborg <sam@ravnborg.org>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCHES] final kbuild update before fix-only period
Date: Sun, 11 Sep 2005 16:00:01 +0200 [thread overview]
Message-ID: <20050911140001.GA7544@mars.ravnborg.org> (raw)
In-Reply-To: <200509111526.58010.vda@ilport.com.ua>
> Hi Sam,
>
> BUG()s etc which are using __FILE__ to get source filename
> print horribly long names like
>
> /.share/usr/src2/kernel/linux-2.6.13-mm2.src/drivers/net/.../some.c
>
> if one builds kernel in separate object dir.
> This is ugly and wastes space in kernel image. Any ideas how to fix this?
I have once experimenting with this on request from Olaf.
The only way I could fine was to pass a new define:
-DKBUILD_FILE='short-file-name' to gcc.
This has the sideeffect that we always accuse the main .c file for
being the culprint.
gcc warns if we override __FILE__
__FILE__ is used in 123 files of wich 26 is within arch/
so it will take a while to change...
I can cook up something if there is interest.
Sam
next prev parent reply other threads:[~2005-09-11 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 20:03 Sam Ravnborg
2005-09-10 20:34 ` [PATCH 1/7] kbuild: add kernelrelease to 'make help' Sam Ravnborg
2005-09-10 20:34 ` [PATCH 2/7] kbuild: CF=<arguments> passes arguments to sparse Sam Ravnborg
2005-09-10 20:35 ` [PATCH 3/7] kbuild: adjust .version updating Sam Ravnborg
2005-09-10 20:36 ` [PATCH 4/7] kbuild: fix split-include dependency Sam Ravnborg
2005-09-10 20:36 ` [PATCH 5/7] kbuild: ignore all debugging info sections in scripts/reference_discarded.pl Sam Ravnborg
2005-09-10 20:37 ` [PATCH 6/7] kbuild: add objectify Sam Ravnborg
2005-09-10 20:38 ` [PATCH 7/7] kbuild: fix generic asm-offsets.h support Sam Ravnborg
2005-09-11 12:26 ` [GIT PATCHES] final kbuild update before fix-only period Denis Vlasenko
2005-09-11 14:00 ` Sam Ravnborg [this message]
2005-09-12 7:19 ` Denis Vlasenko
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=20050911140001.GA7544@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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
all inboxes | Powered by JetHome®