From: "Faccini, Bruno" <bruno.faccini@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Problem to build Kernel 2.4.0 with gcc version "2.96-ia64-000717"
Date: Thu, 11 Jan 2001 23:45:47 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005032@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]
When trying to build Kernel 2.4.0 (from
"http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.0.tar.gz" +
"http://www.kernel.org/pub/linux/kernel/ports/ia64//linux-2.4.0-ia64-010109.
diff.gz" downloads) with gcc version "2.96-ia64-000717" + snap "001117" we
experienced compilation errors with the specific
"net/ipv4/netfilter/ip_tables.c" source file.
After some investigations, it appeared to be due to a problem/regression
with version "2.96-ia64-000717" (+ snap "001117" applied, the gcc pkg
shipped as part of RedHat64 "December-2000" Beta release) to deal with the
following macro in "include/linux/netfilter_ipv4/ip_tables.h" header :
--------------------------------
#define IPT_MATCH_ITERATE(e, fn, args...) \
({ \
unsigned int __i; \
int __ret = 0; \
struct ipt_entry_match *__m; \
\
for (__i = sizeof(struct ipt_entry); \
__i < (e)->target_offset; \
__i += __m->u.match_size) { \
__m = (void *)(e) + __i; \
\
__ret = fn(__m , ## args); \
if (__ret != 0) \
break; \
} \
__ret; \
})
--------------------------------
where "## args" substitution was wrongly done (the first argument in the
"...[,...]" list was garbled depending on its first character, "*" or "&"
are missing if specified and if none the full argument/variable name is
fully missing !!, leading to the compiler error because of 2x"," in a row ).
The simplest way to bypass this was to generate a pre-processed only C
source file, to manually edit+fix the problems/missing characters/names and
to use it as the original source file.
This points to some regression between latest gcc versions vs Linux Kernel
source files content and the syntax used (there was a lot of warnings about
"depracated" use of "##" constructs during the Kernel build but the only
error found) and may be highlights the need of a "generic" gcc ship+use for
Kernel builds ...
Bruno.
<<Bruno Faccini (E-mail).vcf>>
[-- Attachment #2: Bruno Faccini (E-mail).vcf --]
[-- Type: application/octet-stream, Size: 847 bytes --]
BEGIN:VCARD
VERSION:2.1
N:Faccini;Bruno
FN:Bruno Faccini (E-mail)
ORG:Intel;Technical Marketing/Content Group EMEA
TITLE:Tech. Mktg. Engr.
TEL;WORK;VOICE:+33 (0) 146947228
TEL;WORK;VOICE:+33 (0) 155498427
TEL;WORK;FAX:+33 (0) 146947068
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Munich, Germany.;Intel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond Poin=
t Du Pont De Sevres;Boulogne Billancourt;Cedex;92516;France
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Munich, Germany.=0D=0AIntel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond =
Point Du Pont De Sevres=0D=0ABoulogne Billancourt, Cedex 92516=0D=0AFrance
ADR;HOME:;;20 Rue Du Marechal Joffre;Brie Comte Robert;;77170;France
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:20 Rue Du Marechal Joffre=0D=0ABrie Comte Robert 77170=0D=0AFrance
EMAIL;PREF;INTERNET:bruno.faccini@intel.com
REV:20001111T162700Z
END:VCARD
next reply other threads:[~2001-01-11 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 23:45 Faccini, Bruno [this message]
2001-01-12 0:34 ` [Linux-ia64] Problem to build Kernel 2.4.0 with gcc version "2.96-ia64-000717" + snap "001117" Jim Wilson
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=marc-linux-ia64-105590693005032@msgid-missing \
--to=bruno.faccini@intel.com \
--cc=linux-ia64@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