From: Marcel Holtmann <marcel@holtmann.org>
To: Franck Arnaud <franck@nenie.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] LIBS vs LD_FLAGS in bluez-utils makefiles
Date: Thu, 20 May 2004 16:22:52 +0200 [thread overview]
Message-ID: <1085062972.4327.169.camel@pegasus> (raw)
In-Reply-To: <45540213.2004.5.20.13.56.39.93532@mem.nenie.org>
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
next prev parent reply other threads:[~2004-05-20 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 13:56 [Bluez-devel] LIBS vs LD_FLAGS in bluez-utils makefiles Franck Arnaud
2004-05-20 14:22 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 14:00 Franck Arnaud
[not found] <45540213.2004.5.20.21.35.29.45662@mem.nenie.org>
2004-05-21 15:53 ` Marcel Holtmann
2004-05-21 16:40 ` Marcel Holtmann
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=1085062972.4327.169.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=franck@nenie.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