From: "Jörn Engel" <joern@logfs.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-sparse@vger.kernel.org, 505177@bugs.debian.org
Subject: Re: Hard-coded gcc header path
Date: Tue, 11 Nov 2008 15:15:29 +0100 [thread overview]
Message-ID: <20081111141459.GB25986@logfs.org> (raw)
In-Reply-To: <1226412106.4478.5.camel@johannes.berg>
On Tue, 11 November 2008 15:01:46 +0100, Johannes Berg wrote:
>
> Well, sort of. The patch is actually determined at sparse build time, so
> right now sparse requires you to build it against the same compiler that
> you are currently using. If you rebuild sparse with your shiny new
> compiler you'll notice that it'll end up with a different path in
> pre-process.h.
Then the short-term solution for debian is clear. Simply rebuild the
package and add a dependency on a specific gcc version.
Jörn
--
Fantasy is more important than knowledge. Knowledge is limited,
while fantasy embraces the whole world.
-- Albert Einstein
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-11 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 13:58 Hard-coded gcc header path Jörn Engel
2008-11-11 14:01 ` Johannes Berg
2008-11-11 14:15 ` Jörn Engel [this message]
2008-11-11 20:13 ` Bug#505177: " Pierre Habouzit
2008-11-11 20:28 ` Jörn Engel
2008-11-11 21:00 ` Morten Welinder
2008-11-11 22:32 ` Jörn Engel
2008-11-11 23:10 ` Bernd Petrovitsch
2008-11-11 14:41 ` Bernd Petrovitsch
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=20081111141459.GB25986@logfs.org \
--to=joern@logfs.org \
--cc=505177@bugs.debian.org \
--cc=johannes@sipsolutions.net \
--cc=linux-sparse@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).