From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] [PATCH]: don't use functions marked by SUSv3 as legacy
Date: Sun, 1 Jul 2007 16:58:00 +0200 [thread overview]
Message-ID: <200707011658.00819.arekm@maven.pl> (raw)
In-Reply-To: <20070701144829.GI30047@agk.fab.redhat.com>
On Sunday 01 of July 2007, Alasdair G Kergon wrote:
> On Sun, Jul 01, 2007 at 03:29:08PM +0200, Arkadiusz Miskiewicz wrote:
> > Please merge this one:
> > http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/lvm2-susv3.patch
> > by qboosh/pld-linux.org.
>
> Will do. I was brought up on BSD:-)
Please merge this one, too:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/lvm2-as-needed.patch
First it checks for tinfo library in case where ncurses is built in form of
two libraries (tinfo - terminal stuff, ncurses - the rest).
The other one puts LDFLAGS (linker flags) not CFLAGS (cflags is for
compilation, ldflags for linking) and changes order so linking will success
when using -Wl,--as-needed flag.
There are also others mostly self explaining patches for device-mapper:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/device-mapper-disable_dynamic_link.patch
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/device-mapper-force-local-headers.patch
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/device-mapper-getopt.patch
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/device-mapper-klibc.patch
> Alasdair
--
Arkadiusz Mi�kiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next prev parent reply other threads:[~2007-07-01 14:58 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 [this message]
2007-07-01 19:11 ` Nix
2007-07-01 20:36 ` Alasdair G Kergon
2007-07-02 18:47 ` Nix
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=200707011658.00819.arekm@maven.pl \
--to=arekm@maven.pl \
--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 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.