Linux-2.4.4 failure to compile

Linux-2.4.4 failure to compile

[Richard B. Johnson]

Hello;

I downloaded linux-2.4.4. The basic kernel compiles but the aic7xxx
SCSI module that I require on some machines, doesn't. 


[SNIPPED `make modules`]

make -C scsi modules
make[2]: Entering directory `/usr/src/linux-2.4.4/drivers/scsi'
ld -m elf_i386 -r -o scsi_mod.o scsi.o hosts.o scsi_ioctl.o constants.o scsicam.o scsi_proc.o scsi_error.o scsi_obsolete.o scsi_queue.o scsi_lib.o scsi_merge.o scsi_dma.o scsi_scan.o scsi_syms.o
ld -m elf_i386 -r -o initio.o ini9100u.o i91uscsi.o
ld -m elf_i386 -r -o a100u2w.o inia100.o i60uscsi.o
ld -m elf_i386 -r -o sd_mod.o sd.o
ld -m elf_i386 -r -o sr_mod.o sr.o sr_ioctl.o sr_vendor.o
make -C aic7xxx modules
make[3]: Entering directory `/usr/src/linux-2.4.4/drivers/scsi/aic7xxx'
make -C aicasm
make[4]: Entering directory `/usr/src/linux-2.4.4/drivers/scsi/aic7xxx/aicasm'
gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c aicasm_symbol.c -o aicasm
aicasm_gram.y:37: inttypes.h: No such file or directory
aicasm.c:39: inttypes.h: No such file or directory
aicasm_symbol.c:39: db1/db.h: No such file or directory
make[4]: *** [aicasm] Error 1
make[4]: Leaving directory `/usr/src/linux-2.4.4/drivers/scsi/aic7xxx/aicasm'
make[3]: *** [aicasm/aicasm] Error 2
make[3]: Leaving directory `/usr/src/linux-2.4.4/drivers/scsi/aic7xxx'
make[2]: *** [_modsubdir_aic7xxx] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.4/drivers/scsi'
make[1]: *** [_modsubdir_scsi] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.4/drivers'
make: *** [_mod_drivers] Error 2a


Something broke.
A check of ../linux/Documentation/Changes doesn't show that I should
install anything new.


`sh ver_linux`

If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
 
Linux chaos 2.4.1 #10 SMP Fri Feb 23 10:38:40 EST 2001 i686
 
Gnu C                  egcs-2.91.66
Gnu make               3.79.1
binutils               2.9.5.0.16
mount                  2.10o
modutils               2.3.15
e2fsprogs              1.19
PPP                    2.3.10
Linux C Library        > /usr/lib/libc.so.6
Dynamic linker (ldd)   2.0.6
Linux C++ Library      27.1.0
Procps                 1.2
Net-tools              1.50
Kbd                    0.89
Sh-utils               1.12
Modules Loaded         loop ipx 3c59x nls_cp437 BusLogic sd_mod scsi_mod


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

Re: Linux-2.4.4 failure to compile

[Tim Hockin]

"Richard B. Johnson" wrote:
> 
> Hello;
> 
> I downloaded linux-2.4.4. The basic kernel compiles but the aic7xxx
> SCSI module that I require on some machines, doesn't.

The aic7xxx assembler requiring libdb1 is a bungle.  Getting the headers
for that right on various distros is not easy.  Add to that it requires
YACC, when most people have bison (yes, a shell script is easy to make, but
not always an option). 


-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com

Re: Linux-2.4.4 failure to compile

[Christoph Hellwig]

In article <3B040C80.C2A7BC6@sun.com> you wrote:
> "Richard B. Johnson" wrote:
>> 
>> Hello;
>> 
>> I downloaded linux-2.4.4. The basic kernel compiles but the aic7xxx
>> SCSI module that I require on some machines, doesn't.

> The aic7xxx assembler requiring libdb1 is a bungle.  Getting the headers
> for that right on various distros is not easy.  Add to that it requires
> YACC, when most people have bison (yes, a shell script is easy to make, but
> not always an option). 

If make wants to use yacc but you don't have it, it's probably a mistake
in the make(1) configuration - the Makefile uses implicit rules and
distributions not having yacc should not call it in make's implicit rules.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

Re: Linux-2.4.4 failure to compile

[H. Peter Anvin]

Followup to:  <3B040C80.C2A7BC6@sun.com>
By author:    Tim Hockin <thockin@sun.com>
In newsgroup: linux.dev.kernel
> 
> The aic7xxx assembler requiring libdb1 is a bungle.  Getting the headers
> for that right on various distros is not easy.  Add to that it requires
> YACC, when most people have bison (yes, a shell script is easy to make, but
> not always an option). 
> 

Most people have both.  However, if your distribution installs bison
and not yacc and does *NOT* install the "bison as yacc" wrapper, you
should complain to your distributor.

As far as "not always an option", that's ridiculous.  If there really
isn't someone around who can install it globally, then put it in ~/bin
and set your PATH.

The command "yacc" should be expected to work.  This is as insane as
the flamage in the cdrecord documentation about Linux installing GNU
make as "make".

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

Re: Linux-2.4.4 failure to compile

[Richard B. Johnson]

On 17 May 2001, H. Peter Anvin wrote:

> Followup to:  <3B040C80.C2A7BC6@sun.com>
> By author:    Tim Hockin <thockin@sun.com>
> In newsgroup: linux.dev.kernel
> > 
> > The aic7xxx assembler requiring libdb1 is a bungle.  Getting the headers
> > for that right on various distros is not easy.  Add to that it requires
> > YACC, when most people have bison (yes, a shell script is easy to make, but
> > not always an option). 
> > 
> 
> Most people have both.  However, if your distribution installs bison
> and not yacc and does *NOT* install the "bison as yacc" wrapper, you
> should complain to your distributor.
> 
> As far as "not always an option", that's ridiculous.  If there really
> isn't someone around who can install it globally, then put it in ~/bin
> and set your PATH.
> 
> The command "yacc" should be expected to work.  This is as insane as
> the flamage in the cdrecord documentation about Linux installing GNU
> make as "make".
> 
> 	-hpa

I have both. I also have `flex`, but not `lex'. `lex' is a simlink to
flex. What this compile wanted is some header files in expects for
`yacc` that are not present. And they don't come with the `bison`
distribution. Maybe they came with `yacc` years ago? Anyway there
are some poor assumptions being made in the source Makefile.

It would be nice to have the 'microcode' assembler running for
aic7xxx since it is now required for the thing to load.


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

Re: Linux-2.4.4 failure to compile

[H. Peter Anvin]

"Richard B. Johnson" wrote:
> 
> I have both. I also have `flex`, but not `lex'. `lex' is a simlink to
> flex. What this compile wanted is some header files in expects for
> `yacc` that are not present. And they don't come with the `bison`
> distribution. Maybe they came with `yacc` years ago? Anyway there
> are some poor assumptions being made in the source Makefile.
> 
> It would be nice to have the 'microcode' assembler running for
> aic7xxx since it is now required for the thing to load.
> 

It worked just fine with "bison" here (with the appropriate shell script
added.)

I think the header file you're talking about is the db1 header file,
which has nothing to do with yacc -- it's the Berkeley libdb version 1,
which is a pretty bad thing to require.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

Re: Linux-2.4.4 failure to compile

[Lorenzo Marcantonio]

On Thu, 17 May 2001, H. Peter Anvin wrote:

> I think the header file you're talking about is the db1 header file,
> which has nothing to do with yacc -- it's the Berkeley libdb version 1,
> which is a pretty bad thing to require.
>

I've got it to compile (and apparently work) even con libdb3... which
has the compability header db_185.h (or something similar).

IIRC, libdb1 was bundled with libc till release 2.1.3. Since 2.2 they've
said 'get it at sleepycat...'.

BTW, there are ifdef inside the driver about which header to include
(db.h or db_185.h IIRC).

I still doesn't comprend what does it NEED FOR the libdb...

				-- Lorenzo Marcantonio

Re: Linux-2.4.4 failure to compile

[Anuradha Ratnaweera]

On Fri, 18 May 2001, Lorenzo Marcantonio wrote:

> On Thu, 17 May 2001, H. Peter Anvin wrote:
> 
> > I think the header file you're talking about is the db1 header file,
> > which has nothing to do with yacc -- it's the Berkeley libdb version 1,
> > which is a pretty bad thing to require.
> >
> 
> I've got it to compile (and apparently work) even con libdb3... which
> has the compability header db_185.h (or something similar).
> 
> IIRC, libdb1 was bundled with libc till release 2.1.3. Since 2.2 they've
> said 'get it at sleepycat...'.
> 
> BTW, there are ifdef inside the driver about which header to include
> (db.h or db_185.h IIRC).
> 
> I still doesn't comprend what does it NEED FOR the libdb...

I don't do any module programming yet, but the lkmpg lists "Using standard
libraries" under "Common Pitfalls". Is anything unusual going on here?

Anuradha

----------------------------------
http://www.bee.lk/people/anuradha/

Re: Linux-2.4.4 failure to compile

[David Weinehall]

On Fri, May 18, 2001 at 04:41:16PM +0600, Anuradha Ratnaweera wrote:
> 
> On Fri, 18 May 2001, Lorenzo Marcantonio wrote:
> 
> > On Thu, 17 May 2001, H. Peter Anvin wrote:
> > 
> > > I think the header file you're talking about is the db1 header file,
> > > which has nothing to do with yacc -- it's the Berkeley libdb version 1,
> > > which is a pretty bad thing to require.
> > >
> > 
> > I've got it to compile (and apparently work) even con libdb3... which
> > has the compability header db_185.h (or something similar).
> > 
> > IIRC, libdb1 was bundled with libc till release 2.1.3. Since 2.2 they've
> > said 'get it at sleepycat...'.
> > 
> > BTW, there are ifdef inside the driver about which header to include
> > (db.h or db_185.h IIRC).
> > 
> > I still doesn't comprend what does it NEED FOR the libdb...
> 
> I don't do any module programming yet, but the lkmpg lists "Using standard
> libraries" under "Common Pitfalls". Is anything unusual going on here?

Yup. The code in question is not a module, but rather a userspace-program
that generates microcode for the SCSI-adapter(s) in question. As such,
using standard libraries is fully ok. The debate is whether libdb1
is to be considered common enough.


Regards: David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

RE: Linux-2.4.4 failure to compile

[Cress, Andrew R]

Try setting CONFIG_AIC7XXX_BUILD_FIRMWARE=n as a workaround.

-----Original Message-----
From: hch@caldera.de [mailto:hch@caldera.de]
Sent: Thursday, May 17, 2001 2:04 PM
To: thockin@sun.com
Cc: Linux kernel; root@chaos.analogic.com
Subject: Re: Linux-2.4.4 failure to compile


In article <3B040C80.C2A7BC6@sun.com> you wrote:
> "Richard B. Johnson" wrote:
>> 
>> Hello;
>> 
>> I downloaded linux-2.4.4. The basic kernel compiles but the aic7xxx
>> SCSI module that I require on some machines, doesn't.

> The aic7xxx assembler requiring libdb1 is a bungle.  Getting the headers
> for that right on various distros is not easy.  Add to that it requires
> YACC, when most people have bison (yes, a shell script is easy to make,
but
> not always an option). 

If make wants to use yacc but you don't have it, it's probably a mistake
in the make(1) configuration - the Makefile uses implicit rules and
distributions not having yacc should not call it in make's implicit rules.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/