All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-sparse@vger.kernel.org
Subject: Re: sparse (cgcc) vs lintool
Date: Fri, 06 Jun 2008 15:39:16 -0400	[thread overview]
Message-ID: <1212781156.18886.7.camel@dv> (raw)
In-Reply-To: <20080606123434.GA23323@lst.de>

On Fri, 2008-06-06 at 14:34 +0200, Christoph Hellwig wrote:
> When trying to compile xfsprogs (from oss.sgi.com/projects/xfs)
> 
> hch@bigmac:~/work/xfs-cmds/xfsprogs$ CC=~/bin/cgcc ./configure
> hch@bigmac:~/work/xfs-cmds/xfsprogs$ make
> 
> I get this error:
> 
> === libxfs ===
> /usr/bin/libtool --mode=compile /home/hch/bin/cgcc -I. -g -O2 -DNDEBUG
> -DVERSION=\"2.9.8\" -DLOCALEDIR=\"/usr/local/share/locale\"
> -DPACKAGE=\"xfsprogs\" -I../include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> -funsigned-char -fno-strict-aliasing -Wall   -c bit.c
> libtool: compile: unable to infer tagged configuration
> libtool: compile: specify a tag with `--tag'
> make[1]: *** [bit.lo] Error 1
> make: *** [default] Error 2
> 
> Any idea what's up with sparse and libtool?

It can be reproduced without sparse:

[proski@dv xfsprogs-2.9.8]$ ./configure CC=/usr/bin/gcc
checking for gcc... /usr/bin/gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
...
checking size of char *... 8
configure: creating ./config.status
config.status: creating include/builddefs
config.status: creating include/platform_defs.h
config.status: include/platform_defs.h is unchanged
[proski@dv xfsprogs-2.9.8]$ make
=== include ===
rm -f xfs disk
ln -s . xfs
ln -s . disk
=== libxfs ===
/usr/bin/libtool --mode=compile /usr/bin/gcc -I. -g -O2 -DNDEBUG
-DVERSION=\"2.9.8\" -DLOCALEDIR=\"/usr/local/share/locale\" -DPACKAGE=
\"xfsprogs\" -I../include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-funsigned-char -fno-strict-aliasing -Wall   -c bit.c
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
gmake[1]: *** [bit.lo] Error 1
make: *** [default] Error 2
[proski@dv xfsprogs-2.9.8]$

Besides, replying on user installed libtool is asking for trouble.  The
proper way to use libtool is to include it into the package.

It's recommended to use automake with libtool, but even if they are too
automake-averse, there are still some rules how to use libtool properly.

-- 
Regards,
Pavel Roskin

      parent reply	other threads:[~2008-06-06 19:39 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
2008-06-06 13:25       ` Christoph Hellwig
2008-06-06 18:15 ` Uwe Kleine-König
2008-06-06 19:39 ` Pavel Roskin [this message]

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=1212781156.18886.7.camel@dv \
    --to=proski@gnu.org \
    --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 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.