From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: __FILE__ (Re: [PATCH] framework for building modules externally)
Date: Thu, 6 Nov 2008 15:52:52 +0100 [thread overview]
Message-ID: <20081106145252.GA24460@thorin> (raw)
In-Reply-To: <49121300.2050506@t-online.de>
On Wed, Nov 05, 2008 at 10:41:20PM +0100, Christian Franke wrote:
>
> PS: The current use of __FILE__ may also add extra unexpected size: For
> packaging, configure is often run outside of $srcdir with a absolute
> path name. This may result in long __FILE__ strings, like
> /home/maintainer/packaging/grub/tmp/grub-1.96+20081105-1/src/grub-1.96/kern/disk.c
This has annoyed me for a while. Do you know a proper fix?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-11-06 14:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 12:32 [PATCH] framework for building modules externally Robert Millan
2008-11-01 19:02 ` Robert Millan
2008-11-04 18:55 ` Vesa Jääskeläinen
2008-11-04 19:07 ` Robert Millan
2008-11-04 19:13 ` Vesa Jääskeläinen
2008-11-04 19:39 ` Robert Millan
2008-11-05 6:57 ` Christian Franke
2008-11-05 9:42 ` Robert Millan
2008-11-05 21:41 ` Christian Franke
2008-11-06 14:52 ` Robert Millan [this message]
2008-11-06 21:10 ` __FILE__ (Re: [PATCH] framework for building modules externally) Christian Franke
2008-11-07 19:02 ` Robert Millan
2008-11-10 20:39 ` Christian Franke
2008-11-06 14:54 ` [PATCH] framework for building modules externally Robert Millan
2008-11-06 20:43 ` Christian Franke
2008-11-07 19:05 ` Robert Millan
2008-11-08 11:33 ` Robert Millan
2008-11-10 20:44 ` Christian Franke
2009-04-10 23:19 ` phcoder
2009-04-13 13:55 ` Robert Millan
2008-11-05 9:51 ` Robert Millan
2008-11-08 11:29 ` Robert Millan
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=20081106145252.GA24460@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.