From: Martin Steigerwald <Martin@lichtvoll.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Sven Hoexter <sven@timegate.de>, fio@vger.kernel.org
Subject: Re: fio 2.0.8 fails to build on mipsel
Date: Thu, 28 Jun 2012 15:20:01 +0200 [thread overview]
Message-ID: <201206281520.01482.Martin@lichtvoll.de> (raw)
In-Reply-To: <4FEA1A99.7070801@kernel.dk>
Am Dienstag, 26. Juni 2012 schrieb Jens Axboe:
> On 2012-06-26 16:13, Sven Hoexter wrote:
> > On Tue, Jun 26, 2012 at 12:45:30PM +0200, Martin Steigerwald wrote:
> >
> > Hi,
> >
> >> Building fails on mipsel due to¹:
> >> CC server.o
> >>
> >> server.c: In function 'handle_probe_cmd':
> >> server.c:411:15: error: 'arch_mips' undeclared (first use in this
> >> function) server.c:411:15: note: each undeclared identifier is
> >> reported only once for each function it appears in make[1]: ***
> >> [server.o] Error 1
> >> make[1]: Leaving directory
> >> `/build/buildd-fio_2.0.8-1-mipsel-9VXitB/fio-2.0.8' make: ***
> >> [build-stamp] Error 2
> >
> > Adding arch_mips to the enum list at the top of arch/arch.h fixes the
> > build issue, but I've no idea if that's the correct fix, regarding
> > endianess issue etc. Tested on mipsel only, though the build failure
> > happens on mips and mipsel.
>
> It is the right fix, it just needs to have some value. Added.
fio 2.0.8-2 with a build fix for mips/mipsel made it to Debian unstable.
If desired by myself or someone else I may consider backporting it to
Squeeze after it has entered testing.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2012-06-28 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 10:45 fio 2.0.8 fails to build on mipsel Martin Steigerwald
2012-06-26 20:13 ` Sven Hoexter
2012-06-26 20:24 ` Jens Axboe
2012-06-28 13:20 ` Martin Steigerwald [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=201206281520.01482.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sven@timegate.de \
/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