[tulip] Compiling in the tulip driver

Sun, 26 Nov 2000 10:29:12 -0500

Hey Phil,

When I hit the enter key to process the compile-command it compile and
returned to the standard command line prompt. This was only for
pci-scan. I am just as surprised as you.

I did get a message from the assembler on tulip that it had created a
file in /tmp.  I believe this is fairly common.

Jimmy

PS Thanks for the tip about doing a clean custom install-->kernel
development packages. That was the trick for me.

----- Original Message -----
From: "Phil Barone" <pbarone@cfl.rr.com>
To: "james hill" <dragonking7@mediaone.net>
Cc: <tulip@scyld.com>
Sent: Sunday, November 26, 2000 8:06 AM
Subject: RE: [tulip] Compiling in the tulip driver

> Hi Jim,
>   I noticed that you are now up and running, good job. I too am up but
was
> wondering when you said that "The driver and pci-scan has compiled
with no
> complaints.". You are saying that you had absolutely NO warnings when
you
> compiled? Mine compiled but had some warnings that I posted earlier,
though
> everything seems to be working.
>
> > -----Original Message-----
> > From: tulip-admin@scyld.com [mailto:tulip-admin@scyld.com]On Behalf
Of
> > james hill
> > Sent: Saturday, November 25, 2000 12:43 PM
> > To: Dana Lacoste; Donald Becker; David Shochat
> > Cc: tulip list
> > Subject: Re: [tulip] Compiling in the tulip driver
> >
> >
> > Hey David,
> >
> > What I said is/was correct. I had already done the same thing more
times
> > then I care to count. If have currently RH7.0 installed use the
command
> > I gave listed in my post then tell me what you have.
> >
> > However if you do a clean install of RH7.0-->Custom
> > Install--->Everything( as long as you include the kernel
development )
> > you do get the correct path action going for you. But it HAS to be
from
> > a CLEAN install. You CANNOT do it from a currently running
installation.
> > I try that three times.
> >
> > Since I've done that clean install with kernel development
everything is
> > working great. The driver and pci-scan has compiled with no
complaints.
> > Now,  I have both of my systems on my cable modem and it very cool.
It's
> > almost as if I had a plan ( shhh don't tell any one =).
> >
> > Jimmy
> >
> > PS Mr. Becker if you could please update this url
> > http://www.scyld.com/network/updates.html#redhat7.0
> >  with the above information I think it help everybody who has RH7.0
> > especially us newbies.
> >
> >
> > ----- Original Message -----
> > From: "David Shochat" <shochat@acm.org>
> > To: "james hill" <dragonking7@mediaone.net>
> > Cc: "tulip list" <tulip@scyld.com>
> > Sent: Saturday, November 25, 2000 7:41 AM
> > Subject: Re: [tulip] Compiling in the tulip driver
> >
> >
> > > james hill wrote:
> > >
> > > > I have kernel 2.2.16-22smp install currently. I have installed
the
> > > > ***source*** rpm. I am using RH7.0
> > > >
> > > >
> > > >> For example, if you have a RedHat 2.2 kernel-source RPM
installed,
> > > >> (please note ****source****), then since that puts it in
> > > >
> > > > /usr/src/linux
> > > >
> > > >> (against the advice of certain respected people), the switch:
> > > >
> > > >
> > > > if I use the command 'rpm -ivh kernel-2.2.16-22.src.rpm' this
only
> > > > places stuff at two locations:
> > > >
> > > > a bunch files goes to /usr/src/redhat/SOURCES and spec files
goes to
> > > > /usr/src/redhat/SPECS not to /usr/src/linux  There is no
directory
> > path
> > > > my system such as that either real or symbolic.
> > >
> > > After reading your message I figured it was time for a reality
check:
> > >
> > > $ rpm -qpl
> > >
> >
ftp://ftp.valinux.com/pub/mirrors/redhat/redhat/redhat-7.0/i386/en/RedHa
> > t/RPMS/kernel-source-2.2.16-22.i386.rpm
> > > | more
> > > (actually all one line)
> > >
> > > [snip]
> > >
> > > /usr/src/linux-2.2.16/include/linux/adfs_fs_sb.h
> > > /usr/src/linux-2.2.16/include/linux/affs_fs.h
> > > /usr/src/linux-2.2.16/include/linux/affs_fs_i.h
> > > /usr/src/linux-2.2.16/include/linux/affs_fs_sb.h
> > > /usr/src/linux-2.2.16/include/linux/affs_hardblocks.h
> > > /usr/src/linux-2.2.16/include/linux/agp_backend.h
> > > /usr/src/linux-2.2.16/include/linux/agpgart.h
> > > /usr/src/linux-2.2.16/include/linux/amifd.h
> > > /usr/src/linux-2.2.16/include/linux/amifdreg.h
> > > /usr/src/linux-2.2.16/include/linux/amigaffs.h
> > > /usr/src/linux-2.2.16/include/linux/apm_bios.h
> > > /usr/src/linux-2.2.16/include/linux/arcdevice.h
> > > /usr/src/linux-2.2.16/include/linux/atalk.h
> > > /usr/src/linux-2.2.16/include/linux/atari_rootsec.h
> > > /usr/src/linux-2.2.16/include/linux/auto_fs.h
> > > /usr/src/linux-2.2.16/include/linux/autoconf.h
> > > /usr/src/linux-2.2.16/include/linux/awe_voice.h
> > > /usr/src/linux-2.2.16/include/linux/ax25.h
> > > /usr/src/linux-2.2.16/include/linux/b1lli.h
> > > /usr/src/linux-2.2.16/include/linux/b1pcmcia.h
> > > /usr/src/linux-2.2.16/include/linux/baycom.h
> > > /usr/src/linux-2.2.16/include/linux/bigmem.h
> > >
> > > So the source RPM really does install the source in
> > > /usr/src/linux-2.2.16 (including the 2.2 header files which are
all
> > you
> > > really need). You do not need to recompile the kernel itself.
> > >
> > > I thought it also created the symbolic link linux->linux-2.2.16
too.
> > If
> > > not, you can certainly create it yourself.
> > >
> > > Or, just forget about the symbolic link and use
> > > -I/usr/src/linux-2.2.16/include
> > >
> > > in your compile command.
> > >
> > > However, this may be water under the bridge by now since it seems
you
> > > did get a successful compile. I just wanted to set the record
straight
> > > about where the RedHat kernel source RPM puts its files.
> > > -- David
> > >
> >
> >
> > _______________________________________________
> > tulip mailing list
> > tulip@scyld.com
> > http://www.scyld.com/mailman/listinfo/tulip
>