From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Small fixes for ocfs2-tools 1.1.1
Date: Sat Aug 20 18:36:48 2005 [thread overview]
Message-ID: <20050820233652.GA10981@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050820213222.GR4436@marowsky-bree.de>
On Sat, Aug 20, 2005 at 11:32:22PM +0200, Lars Marowsky-Bree wrote:
> On 2005-08-20T13:48:13, Manish Singh <manish.singh@oracle.com> wrote:
>
> > > The second one I'm not sure about whether you want to take it upstream.
> > > If linking against com_err, you need to also link against pthread now.
> > What changed to require this? That sounds kind of broken, and isn't
> > reflected in upstream e2fsprogs.
>
> I investigated in some more detail, and this seems to be our fault ;-)
> We have a patch which adds mutex locking to e2fsprogs. Looks like
> the libraries were made thread-safe(r). I've pinged the maintainer
> if/why the patch is not upstream.
Hm, then the patch needs work. com_err should be built and linked with
-pthread, so it gets a shared library dependency on libpthread, so this
becomes a non-issue. com_err.pc should also have -pthread in Cflags and
Libs.
To get it upstream, there's much more work involved, since e2fsprogs
supports more than just Linux. The incantations required to compile
against pthreads differ in subtle ways across the various platforms.
I'd suggest reverting the change until something is worked out upstream,
so there's no gratuitous incompatibilities.
-Manish
next prev parent reply other threads:[~2005-08-20 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 9:19 [Ocfs2-devel] Small fixes for ocfs2-tools 1.1.1 Lars Marowsky-Bree
2005-08-20 15:48 ` Manish Singh
2005-08-20 16:32 ` Lars Marowsky-Bree
2005-08-20 18:36 ` Manish Singh [this message]
2005-08-21 23:01 ` Joel Becker
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=20050820233652.GA10981@ca-server1.us.oracle.com \
--to=manish.singh@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.