From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [STABLE][PATCH] sqlite: use LDFLAGS (fixes QA error)
Date: Sun, 05 Apr 2009 16:38:08 +0200 [thread overview]
Message-ID: <grafog$2h4$2@ger.gmane.org> (raw)
In-Reply-To: <1238927767-18963-1-git-send-email-jeremy.laine@bolloretelecom.eu>
On 05-04-09 12:36, Jeremy Lainé wrote:
> From: Jeremy Lainé<jeremy.laine@m4x.org>
Acked-by: Koen Kooi <koen@openembedded.org>
>
>
> Signed-off-by: Jeremy Lainé<jeremy.laine@m4x.org>
> ---
> .../sqlite-2.8.17/mainmk_build_dynamic.patch | 18 ++++++++++--------
> recipes/sqlite/sqlite_2.8.17.bb | 2 +-
> 2 files changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/recipes/sqlite/sqlite-2.8.17/mainmk_build_dynamic.patch b/recipes/sqlite/sqlite-2.8.17/mainmk_build_dynamic.patch
> index e936f81..914422f 100644
> --- a/recipes/sqlite/sqlite-2.8.17/mainmk_build_dynamic.patch
> +++ b/recipes/sqlite/sqlite-2.8.17/mainmk_build_dynamic.patch
> @@ -1,6 +1,6 @@
> -diff -bur sqlite-2.8.17~orig/main.mk sqlite-2.8.17/main.mk
> ---- sqlite-2.8.17~orig/main.mk 2005-04-23 17:43:23.000000000 -0500
> -+++ sqlite-2.8.17/main.mk 2006-02-13 03:31:03.000000000 -0600
> +diff -urN sqlite-2.8.17.orig/main.mk sqlite-2.8.17/main.mk
> +--- sqlite-2.8.17.orig/main.mk 2005-04-23 22:43:23.000000000 +0000
> ++++ sqlite-2.8.17/main.mk 2009-04-02 20:10:36.000000000 +0000
> @@ -139,7 +139,7 @@
> # This is the default Makefile target. The objects listed here
> # are what get build when you type just "make" with no arguments.
> @@ -17,13 +17,15 @@ diff -bur sqlite-2.8.17~orig/main.mk sqlite-2.8.17/main.mk
> -libsqlite.a: $(LIBOBJ)
> - $(AR) libsqlite.a $(LIBOBJ)
> - $(RANLIB) libsqlite.a
> -+libsqlite.so: $(LIBOBJ)
> -+ $(CC) -shared -o libsqlite.so -Wl,-soname,libsqlite.so.0 $(LIBOBJ)
> -
> +-
> -sqlite$(EXE): $(TOP)/src/shell.c libsqlite.a sqlite.h
> -+sqlite$(EXE): $(TOP)/src/shell.c libsqlite.so sqlite.h
> - $(TCCX) $(READLINE_FLAGS) -o sqlite$(EXE) $(TOP)/src/shell.c \
> +- $(TCCX) $(READLINE_FLAGS) -o sqlite$(EXE) $(TOP)/src/shell.c \
> - libsqlite.a $(LIBREADLINE) $(THREADLIB)
> ++libsqlite.so: $(LIBOBJ)
> ++ $(CC) $(LDFLAGS) -shared -o libsqlite.so -Wl,-soname,libsqlite.so.0 $(LIBOBJ)
> ++
> ++sqlite$(EXE): $(TOP)/src/shell.c libsqlite.so sqlite.h
> ++ $(TCCX) $(LDFLAGS) $(READLINE_FLAGS) -o sqlite$(EXE) $(TOP)/src/shell.c \
> + -lsqlite $(LIBREADLINE) $(THREADLIB)
>
> sqlite_analyzer$(EXE): $(TOP)/src/tclsqlite.c libsqlite.a $(TESTSRC) \
> diff --git a/recipes/sqlite/sqlite_2.8.17.bb b/recipes/sqlite/sqlite_2.8.17.bb
> index b5939d9..9f6ec7e 100644
> --- a/recipes/sqlite/sqlite_2.8.17.bb
> +++ b/recipes/sqlite/sqlite_2.8.17.bb
> @@ -4,7 +4,7 @@ SECTION = "libs"
> PRIORITY = "optional"
> DEPENDS = "readline ncurses"
> LICENSE = "PD"
> -PR = "r2"
> +PR = "r3"
>
> SRC_URI = "http://www.hwaci.com/sw/sqlite/sqlite-${PV}.tar.gz \
> file://mainmk_build_dynamic.patch;patch=1 \
prev parent reply other threads:[~2009-04-05 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 10:36 [STABLE][PATCH] sqlite: use LDFLAGS (fixes QA error) Jeremy Lainé
2009-04-05 14:38 ` Koen Kooi [this message]
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='grafog$2h4$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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