From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: compile fails on 2.4.17-pre3
Date: Wed, 05 Dec 2001 14:27:48 -0500 [thread overview]
Message-ID: <3C0E7534.3EC4B202@mandrakesoft.com> (raw)
In-Reply-To: <1007558606.14970.11.camel@plars.austin.ibm.com>
Paul Larson wrote:
>
> Is everybody seeing this and it's obvious, or do I need to send my
> .config?
>
> ld -m elf_i386 -r -o ipv4.o utils.o route.o inetpeer.o proc.o
> protocol.o ip_input.o ip_fragment.o ip_forward.o ip_options.o
> ip_output.o ip_sockglue.o tcp.o tcp_input.o tcp_output.o tcp_timer.o
> tcp_ipv4.o tcp_minisocks.o tcp_diag.o raw.o udp.o arp.o icmp.o devinet.o
> af_inet.o igmp.o sysctl_net_ipv4.o fib_frontend.o fib_semantics.o
> fib_hash.o
> ld: cannot open tcp_diag.o: No such file or directory
> make[3]: *** [ipv4.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/net/ipv4'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux/net/ipv4'
> make[1]: *** [_subdir_ipv4] Error 2
> make[1]: Leaving directory `/usr/src/linux/net'
> make: *** [_dir_net] Error 2
fix:
1) remove "tcp_diag.o" from net/ipv4/Makefile
2) remove two lines from net/ipv4/tcp.c which reference tcpdiag_init
The file is in vger so I assume it's easily fixed by adding that file as
well. http://vger.kernel.org/
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-12-05 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 13:23 compile fails on 2.4.17-pre3 Paul Larson
2001-12-05 13:39 ` Paul Larson
2001-12-05 19:27 ` Jeff Garzik [this message]
2001-12-05 18:32 ` Marcelo Tosatti
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=3C0E7534.3EC4B202@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox