public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: linux-xfs@oss.sgi.com, Timothy Shimmin <tes@sgi.com>
Cc: Gerald Bringhurst <gbringhurst@novell.com>,
	Brandon Philips <bphilips@suse.de>
Subject: acl and attr: libmisc linkage
Date: Sun, 28 Oct 2007 19:04:04 +0100	[thread overview]
Message-ID: <200710281904.04818.agruen@suse.de> (raw)

Hello,

I noticed that in some cases, gcc is unhappy when libmisc.a is specified after 
libattr.so and libacl.so, and doesn't link in stuff from libmisc.a 
(specifically, walk_tree). I don't know the exact reason for this behavior, 
but putting libmisc.a before the dynamic libraries fixes the problem, i.e., 
like this:

  -LLDLIBS = $(LIBACL) $(LIBATTR) $(LIBMISC)
  -LTDEPENDENCIES = $(LIBACL) $(LIBMISC)
  +LLDLIBS = $(LIBMISC) $(LIBACL) $(LIBATTR)
  +LTDEPENDENCIES = $(LIBMISC) $(LIBACL)

Is that acceptable?

Thanks,
Andreas

                 reply	other threads:[~2007-10-28 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200710281904.04818.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=bphilips@suse.de \
    --cc=gbringhurst@novell.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=tes@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox