From: Christoph Hellwig <hch@lst.de>
To: Christoph Hellwig <hch@lst.de>, linux-sparse@vger.kernel.org
Subject: Re: sparse (cgcc) vs lintool
Date: Fri, 6 Jun 2008 15:07:56 +0200 [thread overview]
Message-ID: <20080606130756.GA24879@lst.de> (raw)
In-Reply-To: <20080606124955.GE600@ins.uni-bonn.de>
On Fri, Jun 06, 2008 at 02:49:55PM +0200, Ralf Wildenhues wrote:
> > Any idea what's up with sparse and libtool?
>
> If --tag=CC is not passed to libtool before /home/hch/bin/cgcc, then it
> tries to infer the set of compiler settings to use (CC, CXX, F77, ...)
> from the compiler name passed.
>
> I don't know the sources in question, but typically you can append
> --tag=CC to some $(LIBTOOL) variable or set $(LIBTOOLFLAGS) or so.
Thanks, a
LIBTOOL="libtool --tag=CC" CC=~/bin/cgcc ./configure
does it for me. So I guess the problem is with libtool and it needs
to be taught about cgcc.
next prev parent reply other threads:[~2008-06-06 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 12:34 sparse (cgcc) vs lintool Christoph Hellwig
2008-06-06 12:47 ` Balbir Singh
2008-06-06 12:49 ` Ralf Wildenhues
2008-06-06 13:07 ` Christoph Hellwig [this message]
2008-06-06 13:21 ` Ralf Wildenhues
2008-06-06 13:25 ` Christoph Hellwig
2008-06-06 18:15 ` Uwe Kleine-König
2008-06-06 19:39 ` Pavel Roskin
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=20080606130756.GA24879@lst.de \
--to=hch@lst.de \
--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