From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] e2fsprogs: add a patch to link against SEM_INIT libs
Date: Tue, 6 Oct 2009 18:53:34 +0800 [thread overview]
Message-ID: <1254826414-20763-2-git-send-email-daniel@caiaq.de> (raw)
In-Reply-To: <1254826414-20763-1-git-send-email-daniel@caiaq.de>
This patch is needed to make e2fsprogs being linked against
SEM_INIT libraries. In this particular case, it causes the
Makefiles to add -lpthread. Without that, all binaries crash
at startup, at least on x86.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
---
.../e2fsprogs/e2fsprogs-1.41.9-sem-init-libs.patch | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 package/e2fsprogs/e2fsprogs-1.41.9-sem-init-libs.patch
diff --git a/package/e2fsprogs/e2fsprogs-1.41.9-sem-init-libs.patch b/package/e2fsprogs/e2fsprogs-1.41.9-sem-init-libs.patch
new file mode 100644
index 0000000..56f1cc2
--- /dev/null
+++ b/package/e2fsprogs/e2fsprogs-1.41.9-sem-init-libs.patch
@@ -0,0 +1,11 @@
+--- e2fsprogs-1.41.9/MCONFIG.in.orig 2009-10-07 20:25:07.000000000 +0800
++++ e2fsprogs-1.41.9/MCONFIG.in 2009-10-07 20:21:41.000000000 +0800
+@@ -85,7 +85,7 @@
+ #
+ LIB = $(top_builddir)/lib
+ LIBSS = $(LIB)/libss at LIB_EXT@ @PRIVATE_LIBS_CMT@ @DLOPEN_LIB@
+-LIBCOM_ERR = $(LIB)/libcom_err at LIB_EXT@ @PRIVATE_LIBS_CMT@ @SEM_INIT_LIB@
++LIBCOM_ERR = $(LIB)/libcom_err at LIB_EXT@ @SEM_INIT_LIB@
+ LIBE2P = $(LIB)/libe2p at LIB_EXT@
+ LIBEXT2FS = $(LIB)/libext2fs at LIB_EXT@
+ LIBUUID = @LIBUUID@ @SOCKET_LIB@
--
1.6.0.4
next prev parent reply other threads:[~2009-10-06 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 10:53 [Buildroot] [PATCH] e2fsprogs: bump version number to 1.41.9 Daniel Mack
2009-10-06 10:53 ` Daniel Mack [this message]
2009-10-07 13:33 ` [Buildroot] [PATCH] e2fsprogs: add a patch to link against SEM_INIT libs Peter Korsgaard
2009-10-07 13:41 ` Daniel Mack
2009-10-07 13:56 ` Peter Korsgaard
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=1254826414-20763-2-git-send-email-daniel@caiaq.de \
--to=daniel@caiaq.de \
--cc=buildroot@busybox.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