From: Info <arling@sniip.ru>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: In addition to: Tulip on 2.4.7 stay unworkable both on 21041 and 21142 in 10M net + OOPS
Date: Mon, 13 Aug 2001 18:21:53 +0400 [thread overview]
Message-ID: <01081318215300.01213@sh.lc> (raw)
Hello!
I forgot to place in my previous letter compiler's message about Tulip;
it appeared while I compiled kernel without "new bus" configuration.
This message is (seperated by *********):
___________________________________________________
make[4]: Вход в каталог `/usr/src/linux/drivers/net/tulip'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
eeprom.o eeprom.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
interrupt.o interrupt.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
media.o media.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
timer.o timer.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
tulip_core.o tulip_core.c
****************************************
tulip_core.c: In function `tulip_init_one':
tulip_core.c:1768: warning: label `err_out_free_res' defined but not
used
******************************************
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
21142.o 21142.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -c -o
pnic.o pnic.c
rm -f tulip.o
ld -m elf_i386 -r -o tulip.o eeprom.o interrupt.o media.o timer.o
tulip_core.o 21142.o pnic.o
make[4]: Выход из каталог `/usr/src/linux/drivers/net/tulip'
___________________________________________________
I don't know if this (or such) message appeares when compiling kernel
with "new bus" configuration: I didn't notice it on compiling, and.
sorry., have no oppotunity to repead compiling.
Best regards,
George Afanassew
reply other threads:[~2001-08-13 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01081318215300.01213@sh.lc \
--to=arling@sniip.ru \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@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