From: Denis Cheng <crquan@gmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] for a header-file-cannot-found building error
Date: Wed, 15 Aug 2007 11:27:01 +0800 [thread overview]
Message-ID: <1187148421286-git-send-email-crquan@gmail.com> (raw)
the -idirafter used as a backend including path for header files, but the original style
didn't work, pick a specific gcc command from the making process:
gcc -Wall -g -I. -O2 -idirafter /usr/src/linux-2.6.21.7/include/linux -I//usr/include \
-I../config -I../../cman/lib -I../include/ -I../lib/ -c -o plock.o plock.c
plock.c:37:34: linux/lock_dlm_plock.h: No such file or directory
just because plock.c needs a header file <linux/lock_dlm_plock.h>, this could work:
gcc -Wall -g -I. -O2 -idirafter /usr/src/linux-2.6.21.7/include -I//usr/include \
-I../config -I../../cman/lib -I../include/ -I../lib/ -c -o plock.o plock.c
--- ./cluster-2.00.00/group/dlm_controld/Makefile.orig 2006-08-11 23:18:15.000000000 +0800
+++ ./cluster-2.00.00/group/dlm_controld/Makefile 2007-08-15 11:02:47.000000000 +0800
@@ -17,7 +17,7 @@
CFLAGS+= -g -I${incdir} -I${top_srcdir}/config
-CFLAGS+= -idirafter ${KERNEL_SRC}/include/linux \
+CFLAGS+= -idirafter ${KERNEL_SRC}/include \
-I../../group/lib/ \
-I../../ccs/lib/ \
-I../../cman/lib/ \
--- ./cluster-2.00.00/group/gfs_controld/Makefile.orig 2006-08-11 23:18:15.000000000 +0800
+++ ./cluster-2.00.00/group/gfs_controld/Makefile 2007-08-15 11:02:38.000000000 +0800
@@ -16,7 +16,7 @@
include ${top_srcdir}/make/defines.mk
CFLAGS+= -g -I. -O2 \
- -idirafter ${KERNEL_SRC}/include/linux \
+ -idirafter ${KERNEL_SRC}/include \
-I${incdir} \
-I${top_srcdir}/config \
-I../../cman/lib \
next reply other threads:[~2007-08-15 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 3:27 Denis Cheng [this message]
2007-08-15 18:10 ` [Cluster-devel] [PATCH] for a header-file-cannot-found building error David Teigland
2007-08-16 1:45 ` 程任全
2007-08-19 5:32 ` Fabio Massimo Di Nitto
2007-08-20 14:01 ` David Teigland
2007-08-21 4:48 ` 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=1187148421286-git-send-email-crquan@gmail.com \
--to=crquan@gmail.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.