linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [PATCH]: don't use functions marked by SUSv3 as legacy
Date: Mon, 02 Jul 2007 19:47:57 +0100	[thread overview]
Message-ID: <87k5tiabhe.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20070701203656.GL30047@agk.fab.redhat.com> (Alasdair G. Kergon's message of "Sun, 1 Jul 2007 21:36:56 +0100")

On 1 Jul 2007, Alasdair G. Kergon told this:

> On Sun, Jul 01, 2007 at 08:11:18PM +0100, Nix wrote:
>> There must be more to it than this. I've always built with -Wl,--as-needed
>> (wired into my GCC specs file), and I've never had a problem with LVM.
>  
> This is only changing 'fsadm' which is not enabled by default upstream
> as I don't yet consider it stable.

I build fsadm and I don't need this patch.

(However, without this patch, including -Wl,--as-needed in the LDFLAGS
won't link fsadm with --as-needed, so it is still beneficial. I just
don't see that it's making linking work where before it didn't.)

-- 
`... in the sense that dragons logically follow evolution so they would
 be able to wield metal.' --- Kenneth Eng's colourless green ideas sleep
 furiously

  reply	other threads:[~2007-07-02 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 13:29 [linux-lvm] [PATCH]: don't use functions marked by SUSv3 as legacy Arkadiusz Miskiewicz
2007-07-01 14:48 ` Alasdair G Kergon
2007-07-01 14:58   ` Arkadiusz Miskiewicz
2007-07-01 19:11     ` Nix
2007-07-01 20:36       ` Alasdair G Kergon
2007-07-02 18:47         ` Nix [this message]
2007-07-01 20:34     ` Alasdair G Kergon
2007-07-02  7:21       ` Arkadiusz Miskiewicz

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=87k5tiabhe.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).