trinity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: compile error within a 32 bit KVM
Date: Fri, 22 Jan 2016 19:58:29 +0100	[thread overview]
Message-ID: <56A27BD5.30106@gmx.de> (raw)

Hi

latest HEAD gives :


i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -g -ggdb -Wall -W  -I. -Iinclude/ -Wimplicit  -D_GNU_SOURCE -D__linux__  -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wnested-externs -Wpacked -Wshadow -Wswitch-enum -Wundef -Wwrite-strings -Wno-format-nonliteral -Wstrict-prototypes -Wmissing-prototypes -Wlogical-op -Wstrict-aliasing=3 -Wno-maybe-uninitialized -o rand/random.o -c rand/random.c
rand/random-page.c: In function ‘fabricate_struct’:
rand/random-page.c:67:5: error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode
     for (int j = 0; j < 2; j++) {
     ^
rand/random-page.c:67:5: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
Makefile:108: recipe for target 'rand/random-page.o' failed
make: *** [rand/random-page.o] Error 1
make: *** Waiting for unfinished jobs....
 * ERROR: dev-util/trinity-9::local failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-util/trinity-9::local'`,
 * the complete build log and the output of `emerge -pqv '=dev-util/trinity-9::local'`.
 * The complete build log is located at '/var/log/portage/dev-util:trinity-9:20160122-185702.log.gz'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-util/trinity-9/temp/build.log.gz'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/trinity-9/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-util/trinity-9/work/trinity-9'
 * S: '/var/tmp/portage/dev-util/trinity-9/work/trinity-9'
 *
 * The following package has failed to build, install, or execute postinst:
 *
 *  (dev-util/trinity-9:0/0::local, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/dev-util:trinity-9:20160122-185702.log.gz'




-- 
Toralf, pgp: C4EACDDE 0076E94E

             reply	other threads:[~2016-01-22 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 18:58 Toralf Förster [this message]
     [not found] ` <20160122193524.GA5687@codemonkey.org.uk>
2016-01-22 20:07   ` compile error within a 32 bit KVM Toralf Förster

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=56A27BD5.30106@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=trinity@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).