public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Donald Duckie <schipperke2000@yahoo.com>
To: Richard Adams <pa3gcu@zeelandnet.nl>,
	Linux Newbie Mailing List <linux-newbie@vger.kernel.org>
Subject: Re: Invalid kernel header included in userspace; multi-line string literals are deprecated
Date: Tue, 14 Sep 2004 02:48:38 -0700 (PDT)	[thread overview]
Message-ID: <20040914094838.24782.qmail@web53605.mail.yahoo.com> (raw)
In-Reply-To: <200409141025.10507.pa3gcu@zeelandnet.nl>

hi!

thank you very much :-)
the make mrproper; make oldconfig; and make dep were
all that was lacking . . . whew!!!

for my next steps though, where can i find some
information on snull_load and snull_unload?
running them gave me the following errors:

[aphrodite@aphrodite2 snull]$ snull_load
./snull.o: ELF file ./snull.o not for this
architecture
local0: Host name lookup failure
ifconfig: `--help' gives usage information.
local1: Host name lookup failure
ifconfig: `--help' gives usage information.

[aphrodite@aphrodite2 snull]$ snull_unload
sn0: unknown interface: No such device
sn1: unknown interface: No such device
snull: Operation not permitted



--- Richard Adams <pa3gcu@zeelandnet.nl> wrote:

> On Tuesday 14 September 2004 02:27, Donald Duckie
> wrote:
> > hi!
> >
> > thank you very much for your information.
> > and i'm so sorry for not stating everything that i
> was
> > doing.
> >
> > anyway, i was trying to compile the snull sample
> that
> > i got from
> >
>
http://www.oreilly.com.tw/editor_column/a138_read.html
> 
> Unless you understand the langauage of China then i
> suggest you use, 
> http://www.oreilly.com/ forget the tw.
> 
> > on linux-sh-2.4.18. since i found some problem, i
> > modified the Rules.make (not exactly the Makefile
> as
> > previously mentioned).
> 
> You should not touch that file _at all_.
> 
> >
> > the original errors were:
> > [aphrodite@aphrodite2 snull2]$ make clean;make
> > rm -f *.o *~ core .depend
> > gcc -Wall -D__KERNEL__ -DMODULE
> > -I/usr/src/linux/include -O -g -DSNULL_DEBUG  -I..
> -M
> > snull.c > .depend
> > In file included from
> > /usr/src/linux/include/linux/config.h:4,
> >                  from snull.c:25:
> > /usr/include/linux/autoconf.h:1:2: #error Invalid
> > kernel header included in userspace
> 
> You are indeed doing things _all_ wrong, firstly one
> needs a fully configured 
> kernel source, you do not need to fully compile a
> new kernel simply use your 
> running kernels .config file, most distro's include
> a sample configuration 
> file for the running kernel, it can be found in
> /boot, it could also be 
> located in /usr/src/linux/configs/ (i have seen at
> lease one distro) that 
> does that.
> Now _before doing anything do;
> 
> cd /usr/src/linux
> make mrproper
> 
> Now copy your sample config file to /usr/src/linux
> rename it .config and do 
> the following.
> 
> make oldconfig
> make dep
> 
> change to the directory where you have the snull
> source, i had it in
>  /home/pa3gcu/source/ldd2-samples/snull/
> 
> Now type 'make' in that directory i needed to edit
> nothing, i did get 2 
> warnings but you can safely ignore then, snull.o
> gets created ok.
> 
> Thats it, no going around in circels at all,
> remember one thing, third party 
> code most always depends on a _configured_ kernel
> source, if one has a 
> configured kernel source then files like autoconf.h
> and all the nessacary 
> symlinks are in place and ready to go.
> 
> I compiled snull on a machine running 2.4.26 with
> gcc 3.3.4.
> Considering snull was first written for 2.0.x
> kernels and has been changed to 
> suit most all kernel versions then i see no problem
> with 2.4.18.
> 
> -- 
> If the Linux community is a bunch of theives because
> they
> try to imitate windows programs, then the Windows
> community
> is built on organized crime.
> 
> Regards Richard
> pa3gcu@zeelandnet.nl
> http://people.zeelandnet.nl/pa3gcu/
> 
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at
> http://www.linux-learn.org/faqs
> 



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-09-14  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13  6:52 Invalid kernel header included in userspace; multi-line string literals are deprecated Donald Duckie
2004-09-13 12:06 ` Richard Adams
2004-09-14  0:27   ` Donald Duckie
2004-09-14  8:25     ` Richard Adams
2004-09-14  9:48       ` Donald Duckie [this message]
2004-09-14 15:21         ` Richard Adams
2004-09-15  1:30           ` Donald Duckie
2004-09-15 12:04             ` Richard Adams
2004-09-22  2:51               ` Donald Duckie
2004-09-22 10:23                 ` unresolved symbol __udivsi3_i4 Donald Duckie
2004-10-02  5:49                   ` Richard Adams
2004-10-02  5:45                 ` Invalid kernel header included in userspace; multi-line string literals are deprecated Richard Adams

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=20040914094838.24782.qmail@web53605.mail.yahoo.com \
    --to=schipperke2000@yahoo.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=pa3gcu@zeelandnet.nl \
    /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