From: Andrey Rahmatullin <wrar-alt@mail.ru>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [PATCH] bluez-gnome link fix
Date: Fri, 22 Dec 2006 00:15:20 +0500 [thread overview]
Message-ID: <20061221191520.GC18112@wrars-comp.wrarsdomain> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 222 bytes --]
Hi.
There is a small patch which fixes linking of bluetooth-sendto with
--as-needed linker option (libs should be in command line only after
sources and static libs that use them).
--
WBR, wRAR (ALT Linux Team)
[-- Attachment #1.1.2: bluez-gnome-0.6-alt-link-fixes.patch --]
[-- Type: text/plain, Size: 405 bytes --]
--- bluez-gnome/sendto/Makefile.am.orig 2006-10-22 23:41:40 +0600
+++ bluez-gnome/sendto/Makefile.am 2006-10-31 21:56:02 +0500
@@ -3,7 +3,7 @@
bluetooth_sendto_SOURCES = main.c
-bluetooth_sendto_LDADD = @GTK_LIBS@ @DBUS_LIBS@ $(top_builddir)/common/libcommon.a
+bluetooth_sendto_LDADD = @GTK_LIBS@ $(top_builddir)/common/libcommon.a @DBUS_LIBS@
AM_CFLAGS = @DBUS_CFLAGS@ @GTK_CFLAGS@
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-12-21 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 19:15 Andrey Rahmatullin [this message]
2006-12-21 19:37 ` [Bluez-devel] [PATCH] bluez-gnome link fix Marcel Holtmann
2006-12-21 19:55 ` Andrey Rahmatullin
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=20061221191520.GC18112@wrars-comp.wrarsdomain \
--to=wrar-alt@mail.ru \
--cc=bluez-devel@lists.sourceforge.net \
/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