All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Miller <mike.miller@hp.com>
To: fio@vger.kernel.org
Subject: fio Makefile bug
Date: Thu, 17 Feb 2011 14:16:36 -0600	[thread overview]
Message-ID: <20110217201636.GA11681@beardog.cce.hp.com> (raw)

I ran across this when trying to run make on fio v1.50.

spike:/tmp/fio-1.50 # make
Makefile:25: Extraneous text after `else' directive
Makefile:30: Extraneous text after `else' directive
Makefile:30: *** only one `else' per conditional.  Stop.

OS info:

spike:/tmp/fio-1.50 # cat /etc/issue

Welcome to SUSE Linux Enterprise Server 10 SP4 RC2 (x86_64) - Kernel \r
(\l).

spike:/tmp/fio-1.50 # uname -a
Linux spike 2.6.16.60-0.81.1-smp #1 SMP Tue Feb 8 06:02:54 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux

The offendinding lines:
else ifeq ($(UNAME), SunOS)
  SOURCE += fifo.c lib/strsep.c helpers.c solaris.c engines/posixaio.c \
                engines/solarisaio.c
  LIBS   += -lpthread -ldl -laio -lrt -lnsl -lsocket
  CPPFLAGS += -D__EXTENSIONS__
else ifeq ($(UNAME), FreeBSD)
  SOURCE += helpers.c engines/posixaio.c
  LIBS   += -lpthread -lrt
  CFLAGS += -rdynamic
else ifeq ($(UNAME), NetBSD)
  SOURCE += helpers.c engines/posixaio.c
  LIBS   += -lpthread -lrt
  CFLAGS += -rdynamic
else ifeq ($(UNAME), AIX)
  SOURCE += fifo.c helpers.c lib/getopt_long.c engines/posixaio.c
  LIBS   += -lpthread -ldl -lrt
  CFLAGS += -rdynamic
  CPPFLAGS += -D_LARGE_FILES -D__ppc__
else ifeq ($(UNAME), Darwin)
  SOURCE += helpers.c engines/posixaio.c
  LIBS   += -lpthread -ldl
else ifneq (,$(findstring CYGWIN,$(UNAME)))
  SOURCE += engines/windowsaio.c
  LIBS   += -lpthread -lrt

To workaround it I simply deleted those lines.

-- mikem

             reply	other threads:[~2011-02-17 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 20:16 Mike Miller [this message]
2011-02-17 20:28 ` fio Makefile bug Bruce Cran

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=20110217201636.GA11681@beardog.cce.hp.com \
    --to=mike.miller@hp.com \
    --cc=fio@vger.kernel.org \
    /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.