From: Matt Tucker <tuck@whistlingfish.net>
To: Brandon Low <lostlogic@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] db-3.2.9-r2
Date: Mon, 24 Feb 2003 15:44:23 -0800 [thread overview]
Message-ID: <106700000.1046130263@benzene.cobaltgroup.com> (raw)
In-Reply-To: <101620000.1046129911@benzene.cobaltgroup.com>
-- Matt Tucker <tuck@whistlingfish.net> spake thusly:
> Your compile command for db_dump185 is:
>
> gcc -c -D_GNU_SOURCE -I../dist/../include -D_REENTRANT
> ../dist/../db_dump185/db_dump185.c
>
> whereas on my system it's using:
>
> gcc -I/usr/include/db1 -c -D_GNU_SOURCE -I../dist/../include
> -D_REENTRANT ../dist/../db_dump185/db_dump185.c
>
> This stuff is hard-coded in dist/Makefile.in:
>
> DB185INC= -I/usr/include/db1 -c @CFLAGS@
> -I$(srcdir)/include @CPPFLAGS@
> DB185LIB= -ldb1
> .
> .
> .
> db_dump185@o@: $(srcdir)/db_dump185/db_dump185.c
> $(CC) $(DB185INC) $?
>
> However, it's _NOT_ in Makefile.in.orig, so I assume there's a gentoo
> patch that you're not picking up. 'emerge sync' perhaps?
A followup on this. In db-3.2.9-r2.ebuild, I see:
# We should get dump185 to link against system db1 ..
# <azarah@gentoo.org> (23 Feb 2003)
cp ${S}/dist/Makefile.in ${S}/dist/Makefile.in.orig
sed -e 's:DB185INC=:DB185INC= -I/usr/include/db1:' \
-e 's:DB185LIB=:DB185LIB= -ldb1:' \
${S}/dist/Makefile.in.orig > ${S}/dist/Makefile.in
I'm going to bet that this isn't in your version -- particularly
because the change was apparently made yesterday.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-02-24 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 21:03 [gentoo-dev] db-3.2.9-r2 Brandon Low
2003-02-24 21:39 ` Dave Nellans
2003-02-24 22:39 ` Brandon Low
2003-02-24 23:38 ` Matt Tucker
2003-02-24 23:44 ` Matt Tucker [this message]
2003-02-25 1:15 ` Brandon Low
2003-02-24 21:39 ` Henti Smith
2003-02-24 21:39 ` Jay Pfeifer
2003-02-24 22:25 ` Peter Ruskin
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=106700000.1046130263@benzene.cobaltgroup.com \
--to=tuck@whistlingfish.net \
--cc=gentoo-dev@gentoo.org \
--cc=lostlogic@gentoo.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