Linux LVM users
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Build bugs for lvm 1.0.1
Date: Tue Dec 18 07:20:02 2001	[thread overview]
Message-ID: <20011218132158.GD1189@tykepenguin.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112171205010.30369-100000@halden.devel.redhat.com>

On Mon, Dec 17, 2001 at 12:13:38PM -0500, Trond Eivind Glomsr?d wrote:
> 1) Trying to set group/user on install is evil. It shouldn't be the 
>    default, as this option will fail when you build as non-root  

That's a fair point but not major as the tools will only run as root anyway so
installing them as non-root is not useful.
 
> 2) When using "--without-user --without-group", it tries to install with 
>    user/group of no/no. Needless to say, this fails.

Sounds like a bug.
 
> 3) It has prototypes of lseek64/basename which are incompatible with 
>    glibc. Use "-DGNU_SOURCE -O2" for CFLAGS and enjoy.

The only reason that -O0 is in there is as a workaround for the broken compilers
in Red Hat 7 :-(
 
> 4) It shouldn't look in /usr/src/linux for the linux kernel sources - 
>    look at /lib/modules/`uname -r`/build. Also, the current running kernel 
>    doesn't necesarrily (or for people who package it, almost certainly 
>    doesn't match) what you build it for.  

The purpose of needing a kernel directory is primarily as a target for the
kernel patch and it is overridden with the --with-kernel_dir= configure option.
If the user is rebuilding a new kernel then it is unlikely to be the same one as
they are running so I think using /lib/modules/... is maybe not the best option.

Agreed /usr/src/linux is not always going to be the right place either but
that's why there is an override.

patrick

      reply	other threads:[~2001-12-18  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 11:12 [linux-lvm] Build bugs for lvm 1.0.1 Trond Eivind Glomsrød
2001-12-18  7:20 ` Patrick Caulfield [this message]

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=20011218132158.GD1189@tykepenguin.com \
    --to=caulfield@sistina.com \
    --cc=linux-lvm@sistina.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