Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-sparse@vger.kernel.org
Subject: Re: sparse (cgcc) vs lintool
Date: Fri, 6 Jun 2008 15:21:23 +0200	[thread overview]
Message-ID: <20080606132123.GF600@ins.uni-bonn.de> (raw)
In-Reply-To: <20080606130756.GA24879@lst.de>

* Christoph Hellwig wrote on Fri, Jun 06, 2008 at 03:07:56PM CEST:
> 
> 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.

Well, thing is, the typical way things work is that a libtool script is
generated as part of the configure process, and it sets things for the
$CC, $CXX, etc. used for that configure.  With this package, however,
/usr/bin/libtool is used, and that typically has been configured only
for /usr/bin/gcc etc.

I suppose a distro could add a section for cgcc, yes, or make it assume
--tag=CC for 'cgcc'.  But really passing --tag=CC is the sane thing to
do: the package knows that your code is C code, whereas libtool
inferring it from the command line is error-prone (which is why the tag
check was made stricter in the first place).

Cheers,
Ralf

  reply	other threads:[~2008-06-06 13:21 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
2008-06-06 13:21     ` Ralf Wildenhues [this message]
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=20080606132123.GF600@ins.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=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