From: Adrian Bunk <bunk@stusta.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Ganesh.Venkatesan@intel.com
Cc: linux-kernel@vger.kernel.org, cramerj@intel.com, john.ronciak@intel.com
Subject: 2.4.28-pre4: e1000_main.c gcc 3.4 compile error
Date: Fri, 8 Oct 2004 22:08:49 +0200 [thread overview]
Message-ID: <20041008200849.GS5227@stusta.de> (raw)
In-Reply-To: <20041008112135.GG16028@logos.cnet>
On Fri, Oct 08, 2004 at 08:21:35AM -0300, Marcelo Tosatti wrote:
>...
> Summary of changes from v2.4.28-pre3 to v2.4.28-pre4
> ============================================
>...
> Ganesh Venkatesan:
>...
> o e1000 - white space corrections, other cleanups
>...
The "other cleanups" are moving
e1000_irq_enable/e1000_irq_disable/e1000_rx_checksum around resulting in
at least the following compile error with gcc 3.4:
<-- snip -->
...
gcc-3.4 -D__KERNEL__
-I/home/bunk/linux/kernel-2.4/linux-2.4.28-pre4-full/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-fno-unit-at-a-time -nostdinc -iwithprefix include
-DKBUILD_BASENAME=e1000_main -c -o e1000_main.o e1000_main.c
e1000_main.c: In function `e1000_up':
e1000_main.c:132: sorry, unimplemented: inlining failed in call to
'e1000_irq_enable': function body not available
e1000_main.c:277: sorry, unimplemented: called from here
make[4]: *** [e1000_main.o] Error 1
make[4]: Leaving directory
`/home/bunk/linux/kernel-2.4/linux-2.4.28-pre4-full/drivers/net/e1000'
<-- snip -->
Please drop this changeset.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-10-08 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 11:21 Linux 2.4.28-pre4 Marcelo Tosatti
2004-10-08 20:08 ` Adrian Bunk [this message]
2004-10-09 22:58 ` mdew .
2004-10-11 16:32 ` Brian Lazara
2004-10-11 16:59 ` Manfred Spraul
2004-10-11 17:07 ` Jeff Garzik
2004-10-16 11:30 ` Barry K. Nathan
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=20041008200849.GS5227@stusta.de \
--to=bunk@stusta.de \
--cc=Ganesh.Venkatesan@intel.com \
--cc=cramerj@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.