From: rct@gherkin.frus.com (Bob_Tracy(0000))
To: gibbs@scsiguy.com
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: [PATCH] aicasm Makefile
Date: Tue, 18 Feb 2003 07:04:31 -0600 (CST) [thread overview]
Message-ID: <20030218130431.EC8594EEF@gherkin.frus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
The Makefile for aicasm has been broken since 2.5.48. The order in
which objects are specified on the linker command line *is* significant,
and if "-ldb" is made part of AICASM_CFLAGS rather than appearing after
the "-o $(PROG)", I get an undefined symbol error (__db185_open).
The attached patch is against 2.5.54-2.5.62 inclusive. If anyone is
wondering, yes, this is a repeat posting on this subject (original was
1 December 2002).
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
[-- Attachment #2: patch62_aicasm --]
[-- Type: text/plain, Size: 716 bytes --]
--- linux/drivers/scsi/aic7xxx/aicasm/Makefile~ 2002-12-24 07:09:29.000000000 -0600
+++ linux/drivers/scsi/aic7xxx/aicasm/Makefile 2003-01-07 16:47:01.000000000 -0600
@@ -10,9 +10,10 @@
GENSRCS= $(YSRCS:.y=.c) $(LSRCS:.l=.c)
SRCS= ${CSRCS} ${GENSRCS}
+LIBS= -ldb
CLEANFILES= ${GENSRCS} ${GENHDRS} $(YSRCS:.y=.output)
# Override default kernel CFLAGS. This is a userland app.
-AICASM_CFLAGS:= -I/usr/include -I. -ldb
+AICASM_CFLAGS:= -I/usr/include -I.
YFLAGS= -d
NOMAN= noman
@@ -30,7 +31,7 @@
endif
$(PROG): ${GENHDRS} $(SRCS)
- $(AICASM_CC) $(AICASM_CFLAGS) $(SRCS) -o $(PROG)
+ $(AICASM_CC) $(AICASM_CFLAGS) $(SRCS) -o $(PROG) $(LIBS)
aicdb.h:
@if [ -e "/usr/include/db3/db_185.h" ]; then \
reply other threads:[~2003-02-18 12:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030218130431.EC8594EEF@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®