From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: maps.c:45:2: error: ‘struct map’ has no member named ‘list’
Date: Thu, 05 Dec 2013 17:42:34 +0100 [thread overview]
Message-ID: <52A0ACFA.9040607@gmx.de> (raw)
latest git at a stable Gentoo Linux 32 bit :
s -Wmissing-prototypes -Werror -o maps.o -c maps.c
maps.c: In function ‘dump_maps’:
maps.c:45:2: error: ‘struct map’ has no member named ‘list’
maps.c:45:2: error: ‘struct map’ has no member named ‘list’
maps.c: In function ‘alloc_zero_map’:
maps.c:96:14: error: ‘struct map’ has no member named ‘list’
maps.c:97:24: error: ‘struct map’ has no member named ‘list’
maps.c: In function ‘setup_maps’:i686-pc-linux-gnu-gcc -O2 -march=native -pipe -g -ggdb -Wall -W -I. -Iinclude/ -Wimplicit -D_GNU_SOURCE -Wdeclaration-after-statement -Wformat=2 -Winit-self -Wlogical-op -Wnested-externs -Wpacked -Wshadow -Wstrict-aliasing=3 -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Werror -o params.o -c params.c
maps.c:106:22: error: ‘struct map’ has no member named ‘list’
maps.c: In function ‘get_map’:
maps.c:124:2: error: ‘struct map’ has no member named ‘list’
maps.c:124:2: error: ‘struct map’ has no member named ‘list’
maps.c: In function ‘destroy_maps’:
maps.c:138:26: error: ‘struct map’ has no member named ‘list’
maps.c:144:26: error: ‘struct map’ has no member named ‘list’
maps.c:146:14: error: ‘struct map’ has no member named ‘list’
make: *** [maps.o] Error 1
make: *** Waiting for unfinished jobs....
* ERROR: dev-util/trinity-9999::toralf failed (compile phase):
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next reply other threads:[~2013-12-05 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:42 Toralf Förster [this message]
2013-12-05 22:10 ` maps.c:45:2: error: ‘struct map’ has no member named ‘list’ Dave Jones
2013-12-07 16:18 ` 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=52A0ACFA.9040607@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).