2.4.13: some compilerwarnings...

2.4.13: some compilerwarnings...

[Sven Vermeulen]

No fatal errors or anything, kernel runs fine, but some compilerwarnings...
they could be in other kernelversions too, I only noticed them this time.

~$ make dep
[...]
make -C eicon fastdep
make[6]: Entering directory `/home/nitro/src/linux/drivers/isdn/eicon'
/home/nitro/src/linux/scripts/mkdep -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6  -- Divas_mod.c adapter.h bri.c common.c constant.h divalog.h divas.h dsp_defs.h dspdids.h eicon.h eicon_dsp.h eicon_idi.c eicon_idi.h eicon_io.c eicon_isa.c eicon_isa.h eicon_mod.c eicon_pci.c eicon_pci.h fourbri.c fpga.c idi.c idi.h kprintf.c lincfg.c linchr.c linio.c linsys.c log.c pc.h pc_maint.h pr_pc.h pri.c sys.h uxio.h xlog.c > .depend
make[6]: Leaving directory `/home/nitro/src/linux/drivers/isdn/eicon'
make -C hisax fastdep
md5sum: WARNING: 13 of 13 computed checksums did NOT match
[...]

~$ make bzImage
[...]
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6    -c -o pci-i386.o pci-i386.c
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6    -c -o pci-pc.o pci-pc.c
{standard input}: Assembler messages:
{standard input}:1040: Warning: indirect lcall without `*'
{standard input}:1125: Warning: indirect lcall without `*'
{standard input}:1208: Warning: indirect lcall without `*'
{standard input}:1282: Warning: indirect lcall without `*'
{standard input}:1293: Warning: indirect lcall without `*'
{standard input}:1304: Warning: indirect lcall without `*'
{standard input}:1378: Warning: indirect lcall without `*'
{standard input}:1389: Warning: indirect lcall without `*'
{standard input}:1400: Warning: indirect lcall without `*'
{standard input}:1862: Warning: indirect lcall without `*'
{standard input}:1951: Warning: indirect lcall without `*'
[...]
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6    -c -o msr.o msr.c
gcc -D__KERNEL__ -I/home/nitro/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6    -c -o apm.o apm.c
{standard input}: Assembler messages:
{standard input}:187: Warning: indirect lcall without `*'
{standard input}:282: Warning: indirect lcall without `*'
[...]
gcc -E -D__KERNEL__ -I/home/nitro/src/linux/include -D__BIG_KERNEL__ -traditional -DSVGA_MODE=NORMAL_VGA  bootsect.S -o bbootsect.s
as -o bbootsect.o bbootsect.s
bbootsect.s: Assembler messages:
bbootsect.s:256: Warning: indirect lcall without `*'
[...]
gcc -E -D__KERNEL__ -I/home/nitro/src/linux/include -D__BIG_KERNEL__ -D__ASSEMBLY__ -traditional -DSVGA_MODE=NORMAL_VGA  setup.S -o bsetup.s
as -o bsetup.o bsetup.s
bsetup.s: Assembler messages:
bsetup.s:1459: Warning: indirect lcall without `*'
[...]


btw: gcc-version is 2.96, as-version is 2.11.90.0.8

Keep up the good work!

	Sven Vermeulen

-- 
Unix, MS-DOS and Windows NT (also known as the Good, the Bad and the
Ugly). ~(Matt Welsh)

Re: 2.4.13: some compilerwarnings...

[Dave Jones]

On Wed, 24 Oct 2001, Sven Vermeulen wrote:

> make[6]: Leaving directory `/home/nitro/src/linux/drivers/isdn/eicon'
> make -C hisax fastdep
> md5sum: WARNING: 13 of 13 computed checksums did NOT match

Been there for a while, and should be harmless.
If you really cared, you could add the new md5sums to the script
that does the checking. Can't remember why this changed without
them being updated.  Someone doing Janitor work perhaps?

> {standard input}: Assembler messages:
> {standard input}:1040: Warning: indirect lcall without `*'

AIUI, fixing these would mean breaking compilation with older versions
of binutils.

regards,

Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

Re: 2.4.13: some compilerwarnings...

[Sven Vermeulen]

On Wed, Oct 24, 2001 at 08:07:42PM +0200, Dave Jones wrote:
[ About md5sum warnings about incorrect md5sum's ]
> Been there for a while, and should be harmless.
> If you really cared, you could add the new md5sums to the script
> that does the checking. 

Can't do that. Those md5sum's are there for a reason.

In $LINUXSOURCE/Documentation/isdn/HiSax.cert :

[...]
  If you change the main files of the HiSax ISDN stack, the certification
  will become invalid. Because in most countries it is illegal to connect
  unapproved ISDN equipment to the public network, I have to guarantee that
  changes in HiSax do not affect the certification.

  In order to make a valid certification apparent to the user, I have built
  in some validation checks that are made during the make process. The HiSax
  main files are protected by md5 checksums and the md5sum file is pgp
  signed by myself:
[...]

	Sven Vermeulen
-- 
I develop for Linux for a living, I used to develop for DOS. Going from
DOS to Linux is like trading a glider for an F117. ~(Lawrence Foard)

Re: 2.4.13: some compilerwarnings...

[Dave Jones]

On Wed, 24 Oct 2001, Sven Vermeulen wrote:

> Can't do that. Those md5sum's are there for a reason.
>   If you change the main files of the HiSax ISDN stack, the certification
>   will become invalid. Because in most countries it is illegal to connect
>   unapproved ISDN equipment to the public network, I have to guarantee that
>   changes in HiSax do not affect the certification.

Ah, that'll be why they've been this way for a while then.

*shrug* Just live with it until an official update from the maintainers
I guess.

regards,

Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

Re: 2.4.13: some compilerwarnings...

[André Dahlqvist]

Sven Vermeulen <sven.vermeulen@rug.ac.be> wrote:

> {standard input}:1040: Warning: indirect lcall without `*'
> {standard input}:1125: Warning: indirect lcall without `*'
> {standard input}:1208: Warning: indirect lcall without `*'

I think Alan once mentioned that this was sort of a feature to make old
versions of binutils work too. I'm not sure exactly how old those are
though, and if they are older than the recommended 2.9.1.0.25 I vote for
fixing these ugly warnings.
-- 

André Dahlqvist <andre.dahlqvist@telia.com>

Re: 2.4.13: some compilerwarnings...

[Alan Cox]

> Sven Vermeulen <sven.vermeulen@rug.ac.be> wrote:
> 
> > {standard input}:1040: Warning: indirect lcall without `*'
> > {standard input}:1125: Warning: indirect lcall without `*'
> > {standard input}:1208: Warning: indirect lcall without `*'
> 
> I think Alan once mentioned that this was sort of a feature to make old
> versions of binutils work too. I'm not sure exactly how old those are
> though, and if they are older than the recommended 2.9.1.0.25 I vote fo=
> r
> fixing these ugly warnings.

Kill them in 2.5, there really isnt a hurry. If it bugs you that much
write yourself a scripts/asm AS:= target that is as 2>&1 | grep -v 8)