From: Jim Cromie <jcromie@divsol.com>
To: "linux-lvm@sistina.com" <linux-lvm@sistina.com>
Subject: [linux-lvm] patch to fix segfault complaints.
Date: Tue Nov 13 10:50:02 2001 [thread overview]
Message-ID: <3BF14F8E.477BC73E@divsol.com> (raw)
others have noted various segfaults,
ex:
>>vgextend -- extending volume group "vg01" by physical volume
"/dev/hde1"
>>in kernel
>>Segmentation fault (core dumped)
This patch fixes configure script to build good (no segfault) lvm tools
for me
theres probably a more comprehensive way to do this, ymmv.
note also that Im only checking for 2.96, not 2.96-85. this may or may
not matter
[root@groucho 1.0.1-rc4]# diff -u configure configure~
--- configure Tue Nov 13 09:35:54 2001
+++ configure~ Thu Sep 6 07:02:34 2001
@@ -796,33 +796,22 @@
fi
-${CC-cc} -v 2>&1 | grep -l 2.96
-if [ $? = 0 ] ; then
- echo "this gcc version breaks with -g -O2"
- optimize=1
-else
- optimize=2
-fi
-
echo "$ac_t""$ac_cv_prog_cc_g" 1>&6
if test "$ac_test_CFLAGS" = set; then
CFLAGS="$ac_save_CFLAGS"
elif test $ac_cv_prog_cc_g = yes; then
if test "$GCC" = yes; then
- CFLAGS="-g -O$optimize"
+ CFLAGS="-g -O2"
else
CFLAGS="-g"
fi
else
if test "$GCC" = yes; then
- CFLAGS="-O$optimize"
+ CFLAGS="-O2"
else
CFLAGS=
fi
fi
# Find a good install program. We prefer a C program (faster),
# so one script is as good as another. But avoid the broken or
next reply other threads:[~2001-11-13 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 10:50 Jim Cromie [this message]
[not found] ` <20011114013315.A3564@tiger.bigcats.invalid>
2001-11-14 13:10 ` [linux-lvm] patch to fix segfault complaints Jim Cromie
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=3BF14F8E.477BC73E@divsol.com \
--to=jcromie@divsol.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