From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] LIBS vs LD_FLAGS in bluez-utils makefiles From: Marcel Holtmann To: Franck Arnaud Cc: BlueZ Mailing List In-Reply-To: <45540213.2004.5.20.13.56.39.93532@mem.nenie.org> References: <45540213.2004.5.20.13.56.39.93532@mem.nenie.org> Content-Type: text/plain Message-Id: <1085062972.4327.169.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 20 May 2004 16:22:52 +0200 Hi Franck, > In bluez-utils's Makefile.am files, it usually says: > > LDFLAGS = @BLUEZ_LIBS@ > > which fails when linking statically, apparently because it's too > early in the command line ("gcc ... -l ... -o ... foo.o"). I don't > think the lib description is a "flag" as intended for $LDFLAGS. > > I replaced the above with > > $LIBS = @BLUEZ_LIBS@ > > so that -l is after the .o files, and linking now succeeds. do this still works with dynamic linking? What about sending a patch for this? Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel