All of lore.kernel.org
 help / color / mirror / Atom feed
From: "omit_ECE" <omit@rice.edu>
To: <linux-kernel@vger.kernel.org>
Subject: linux-kernel@vger.kernel.org
Date: Sun, 29 Sep 2002 20:13:56 -0500	[thread overview]
Message-ID: <00d601c2681e$a60c3280$7f71a018@OMIT> (raw)

Hi,

I want to know the one-way trip time in TCP header.
In tcp_input.c , I found many functions under which include
rcv_tsval and  rcv_tsecr . I don't know which two are right.
So, I put many "printf" and fprintf in functions and compile the kernel.
But when compiling it, some errors happen,

net/network.o: In function `tcp_parse_options':
net/network.o: In function `tcp_rcv_established':
net/network.o: In function `tcp_rcv_synsent_state_process':
net/network.o: In function `tcp_rcv_state_process':
net/network.o(.text+0x2807b): undefined reference to `printf'
net/network.o(.text+0x2808c): undefined reference to `printf'
net/network.o(.text+0x2631d): undefined reference to `fopen'
net/network.o(.text+0x26334): undefined reference to `fprintf'
net/network.o(.text+0x2634e): undefined reference to `fprintf'
net/network.o(.text+0x2635a): undefined reference to `fclose'

Aren't "printf" and "fprintf"  standard outputs? I also put #include <stdio.h>
and "FILE *in_file", but they didn't work. Please give me suggestions.
Thank you.

             reply	other threads:[~2002-09-30  1:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30  1:13 omit_ECE [this message]
2002-09-30  1:18 ` linux-kernel@vger.kernel.org David S. Miller
2002-09-30  1:39 ` linux-kernel@vger.kernel.org Jeff Chua
  -- strict thread matches above, loose matches on Subject: below --
2022-10-14  8:51 linux-kernel@vger.kernel.org Mustafa Ayvaz
2011-01-24 16:43 linux-kernel@vger.kernel.org sen wang
2010-05-29 11:22 linux-kernel@vger.kernel.org uwaysi.bin.kareem
2009-10-11  6:22 linux-kernel@vger.kernel.org Boyan
     [not found] <de72ca4e0905172314q3c55ec52ic9ab762a0352a91d@mail.gmail.com>
2009-05-18  7:06 ` linux-kernel@vger.kernel.org Sudarshan Soma
2008-03-09 17:02 linux-kernel@vger.kernel.org bruno.roussel
2007-08-14  9:58 linux-kernel@vger.kernel.org bizu
2007-08-14  9:58 linux-kernel@vger.kernel.org bizu
2005-07-05 13:58 Linux-kernel@vger.kernel.org linux-kernel
2004-07-26 15:44 linux-kernel@vger.kernel.org rap
2004-07-26 14:48 LINUX-KERNEL@VGER.KERNEL.ORG Returned mail
2004-06-21  9:19 linux-kernel@vger.kernel.org Romia Fersi
2003-06-18 21:46 linux-kernel@vger.kernel.org David Mosberger
2002-10-30 17:57 linux-kernel@vger.kernel.org Manfred Spraul
2002-10-30 21:22 ` linux-kernel@vger.kernel.org Bill Davidsen
2002-01-31  1:02 linux-kernel@vger.kernel.org Ulrich Weigand
2002-01-31  1:11 ` linux-kernel@vger.kernel.org Andrew Morton
2001-05-25 12:42 linux-kernel@vger.kernel.org Julien Laganier

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='00d601c2681e$a60c3280$7f71a018@OMIT' \
    --to=omit@rice.edu \
    --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 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.