public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommy McCabe <rocketjet314@yahoo.com>
To: linux-8086@vger.kernel.org
Subject: Re: Vjhc patch
Date: Mon, 19 Jul 2004 11:51:17 -0700 (PDT)	[thread overview]
Message-ID: <20040719185117.39661.qmail@web51309.mail.yahoo.com> (raw)
In-Reply-To: <20040719180656.GO2830@duckman.distro.conectiva>

--- Eduardo Pereira Habkost
<ehabkost@conectiva.com.br> wrote:
> On Mon, Jul 19, 2004 at 10:53:41AM -0700, Tommy
> McCabe wrote:
> <snip>
> > 
> > Look at vjhc.h. There are two definitions of
> DEFUN,
> > depending on some parameter. One defines a
> function.
> > The other doesn't. For some reason, the parameter
> got
> > changed over the years, so now anything using
> DEFUn
> > comes out as gibberish to the compiler.
> 
> The first one uses ansi function declaration, the
> other K&R function
> declarations. DEFUN is used to make vjhc support
> both.
>
> I can't see where is the error. As I said before:
> ktcp (including vjhc.c)
> builds cleanly on my system, and I would like to
> know which error occurs
> on your system.

1. What version of ELKS and BCC do you have?
2. Did you turn on SLIP header compression in the ELKS
kernel config?

> -- 
> Eduardo
> 

> ATTACHMENT part 2 application/pgp-signature 




		
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/


  reply	other threads:[~2004-07-19 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17 23:51 Vjhc patch Tommy McCabe
2004-07-19 15:23 ` Eduardo Pereira Habkost
2004-07-19 17:53   ` Tommy McCabe
2004-07-19 18:06     ` Eduardo Pereira Habkost
2004-07-19 18:51       ` Tommy McCabe [this message]
2004-07-19 19:01         ` Eduardo Pereira Habkost
2004-07-19 20:57           ` Tommy McCabe

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=20040719185117.39661.qmail@web51309.mail.yahoo.com \
    --to=rocketjet314@yahoo.com \
    --cc=linux-8086@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