Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 1632 invoked from network); 15 Nov 2005 20:36:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Nov 2005 20:36:30 -0000 Received: (qmail 30181 invoked by uid 500); 15 Nov 2005 20:36:30 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 29957 invoked by uid 500); 15 Nov 2005 20:36:28 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 29946 invoked by uid 99); 15 Nov 2005 20:36:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2005 12:36:28 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [206.47.199.165] (HELO simmts7-srv.bellnexxia.net) (206.47.199.165) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2005 12:36:19 -0800 Received: from [192.168.0.4] ([65.95.229.107]) by simmts7-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20051115203606.CNBP23474.simmts7-srv.bellnexxia.net@[192.168.0.4]>; Tue, 15 Nov 2005 15:36:06 -0500 Message-ID: <437A46D7.4020008@pearsoncmg.com> Date: Tue, 15 Nov 2005 15:36:39 -0500 From: Chris Darroch Organization: Pearson CMG User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 X-Accept-Language: en-ca, en-us MIME-Version: 1.0 To: dev@apr.apache.org Subject: Re: apr-util config, etc. References: <437A3E66.8020707@pearsoncmg.com> In-Reply-To: X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Justin: >> My ultimate question, for the impatient, is whether adding >> -R to APRUTIL_LDFLAGS is an appropriate solution when using >> libraries that one expects not to have accompanying .la files. > > We've had this discussion several times. There's a group of developers who > believe we should automatically add the -R flags and an equally vocal > developers who believe that the user must hand-edit ldconfig on their > platform. > > At the moment, the folks who advocate not having the -R flag represent our > state of affairs. OK, understood, and sorry to recapitulate an old discussion. (Also apologies for the strange subject line -- too much proofreading of the body!) > Setting LDFLAGS before running configure should work, like so: > > LDFLAGS="-R/path/to/lib" \ > ./configure > > is an acceptable workaround that should work. It's what I use. I do the same to get Berkeley DB to work with apr-util, with the -Wl,-R option. That seems to be sufficient to ensure that configure's test programs compile and execute. (For some reason, just having -L doesn't do it, and configure wrongly decides that BDB can't be found because one of the test programs fails.) However, if I read the situation correctly, that LDFLAGS setting doesn't actually make it into make process itself; certainly it doesn't turn up outside of config.{log,nice,status} or in make's output. And in both the "fake" libiconv and "real" Oracle instances I've tried, adding either -R or -Wl,-R to LDFLAGS or NOTEST_LDFLAGS, etc., before running configure has no effect; libaprutil-1.so is still built with an unresolved "not found" dependency, because of the missing .la file and the fact that no -R option makes it from my env vars into the make process. Now, maybe that's some other kind of problem -- should one be able to do "NOTEST_LDFLAGS=... ./configure" and have those values appear in, perhaps, build/rules.mk? I'm not sure if that's the intention or not from the comments in rules.mk. At any rate, I've still got a problem on my hands, because to deal with Oracle I need to get something into $LINK after $COMPILE, which means one of LDFLAGS, EXTRA_LDFLAGS, or NOTEST_LDFLAGS in build/rules.mk. No amount of fiddling with prior-to-configure env vars has allowed me to do this; although things turn up in config.nice, they don't make it into the actual make process. Any help appreciated! Thanks! Chris. -- GPG Key ID: 366A375B GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B