From: Robert Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: Problems with recent Makefile changes
Date: Thu, 03 May 2007 09:13:02 -0500 [thread overview]
Message-ID: <4639EDEE.6040104@redhat.com> (raw)
In-Reply-To: <46389943.4050504@ubuntu.com>
Fabio Massimo Di Nitto wrote:
> It would be lovely if you could show me the full error next time it happens
> and if you have a way to reproduce it.
>
> Thanks
> Fabio
>
Hi Fabio,
The problem seems to be that all the include files are somehow specified on
the gcc command if only one file changes. Thus, if I change rgrp.c and do
a make, I get:
[root at trin-10 ../cluster/gfs/gfs_fsck]# make
gcc -Wall -I/home/devel/HEAD.intermediate/cluster/config -D_FILE_OFFSET_BITS=64 -DHELPER_PROGRAM -DGFS_RELEASE_NAME=\"DEVEL.1178030462\" -MMD -O2 -I../include -c -o rgrp.o rgrp.c util.h fsck_incore.h ondisk.h ../include/osi_list.h ../include/osi_user.h ../include/global.h ../include/linux_endian.h fs_bits.h rgrp.h fsck.h log.h block_list.h bitmap.h bio.h fs_inode.h inode.h
gcc: cannot specify -o with -c or -S with multiple files
make: *** [rgrp.o] Error 1
However, I can do "make clean ; make" and it works just fine.
This is a gfs userland example, but I think gfs2 is the same.
Regards,
Bob Peterson
Red Hat Cluster Suite
next prev parent reply other threads:[~2007-05-03 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 13:48 [Cluster-devel] Problems with recent Makefile changes Robert Peterson
2007-05-02 13:59 ` [Cluster-devel] " Fabio Massimo Di Nitto
2007-05-03 14:13 ` Robert Peterson [this message]
2007-05-03 14:52 ` Fabio Massimo Di Nitto
2007-05-03 15:49 ` Alasdair G Kergon
2007-05-03 16:13 ` Fabio Massimo Di Nitto
2007-05-03 16:58 ` Fabio Massimo Di Nitto
2007-05-03 7:50 ` Fabio Massimo Di Nitto
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=4639EDEE.6040104@redhat.com \
--to=rpeterso@redhat.com \
/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.