Linux LVM users
 help / color / mirror / Atom feed
From: Ernesto Silva <silva@athenea.ort.edu.uy>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] K=2.4.3 - LVM0.9.1.B7 compiling problem.
Date: Tue, 24 Apr 2001 13:09:19 -0300	[thread overview]
Message-ID: <01042413111705.07748@pc-silva> (raw)
In-Reply-To: <20010424104505.F9882@sistina.com>

I'm using gcc 2.96 from RedHat 7.0 and I downloaded the tarball.
I also applied the patch from the tarball to the kernel.

On Tue, 24 Apr 2001, you wrote:
> 
> On Tue, Apr 24, 2001 at 12:19:45PM -0300, Ernesto Silva wrote:
> > Hi,
> > 
> > 	In order to make things right I downloaded the 2.4.3 kernel and
> > compiled it (i386).
> > 
> > 	With the new kernel running (lvm-mod load ok) I'm trying to compile lvm
> > tools, but there are lots of warinigs, all the same thing, the first of them is:
> > -----------------------------------------------------------
> > gcc -c -pipe -g -O2 -Wall -DDEBUG -I ../../tools/lib -I ../../tools - debug.o
> > debug.c
> > In file included from ../../tools/lib/liblvm.h:97
> > 		from basename.c:34
> > ../../tools/lib/lvm_log.h:47:59: warning: nothing can be pasted after this token
>  <...snip...> 
> > Does anyone had a problem like this before???
> 
> Hmm...I don't get that at all!  Which version of GCC are you using?  Did you
> download the 0.9.1_beta7 tarball or grab something from the cvs?
> 
> Regards,
> -- 
> AJ Lewis
> Sistina Software Inc.                  Voice:  612-379-3951
> 1313 5th St SE, Suite 111              Fax:    612-379-3952
> Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
> http://www.sistina.com
> 
> Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
> Get my key at: http://www.sistina.com/~lewis/gpgkey
>  (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
> 
> -----Begin Obligatory Humorous Quote----------------------------------------
> THE LESSER-KNOWN PROGRAMMING LANGUAGES #16:
> C- This language was named for the grade received by its creator when he
> submitted it as a class project in a graduate programming class.  C- is
> best described as a "low-level" programming language.  In fact, the
> language generally requires more C- statements than machine-code statements
> to execute a given task.  In this respect, it is very similar to COBOL.
> -----End Obligatory Humorous Quote------------------------------------------
> 

----------------------------------------
Content-Type: application/pgp-signature; name="unnamed"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------

  reply	other threads:[~2001-04-24 16:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 15:19 [linux-lvm] K=2.4.3 - LVM0.9.1.B7 compiling problem Ernesto Silva
2001-04-24 15:45 ` AJ Lewis
2001-04-24 16:09   ` Ernesto Silva [this message]
2001-04-25 14:30     ` Patrick Caulfield
2001-04-25 14:44       ` Joe Thornber
2001-04-25 15:07         ` Patrick Caulfield
2001-04-25  3:19   ` S. Michael Denton
2001-04-25  8:01   ` Patrick Caulfield
2001-04-25 15:55     ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24 17:21 Paulo Fessel
2001-04-24 18:37 ` Ernesto Silva
2001-04-25 13:11   ` Ernesto Silva

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=01042413111705.07748@pc-silva \
    --to=silva@athenea.ort.edu.uy \
    --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