From: tomas szepe <kala@pinerecords.com>
To: Alastair Stevens <alastair.stevens@mrc-bsu.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile failure: 2.4.19-pre7-ac3
Date: Mon, 29 Apr 2002 16:40:12 +0200 [thread overview]
Message-ID: <20020429144012.GC24016@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0204291333460.13800-100000@gerber>
Apparently gcc 2.95.3 goes signal-11 while gcc 2.96 and 3.0.4 (didn't
try any other) blast the above.
t.
> Alan et al: I got the following error from the sound drivers when
> compiling 2.4.19-pre7-ac3 on a dual Athlon machine under RH7.2 (fully
> updated). I had previously compiled -ac1 without any problems, and my
> .config hasn't changed. I ran the usual "make distclean" and then
> "oldconfig dep clean modules bzImage" etc:
>
> gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
> -DMODULE -DMODVERSIONS -include
> /home/alastair/linux-2.4/include/linux/modversions.h -nostdinc -I
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
> -DKBUILD_BASENAME=aic7xxx_pci -c -o aic7xxx_pci.o aic7xxx_pci.c
> ld -m elf_i386 -r -o aic7xxx.o aic7xxx_osm.o aic7xxx_proc.o
> aic7770_osm.o aic7xxx_osm_pci.o aic7xxx_core.o aic7xxx_93cx6.o aic7770.o
> aic7xxx_pci.o
> make[3]: Leaving directory
> `/home/alastair/linux-2.4/drivers/scsi/aic7xxx'
> make[2]: Leaving directory `/home/alastair/linux-2.4/drivers/scsi'
> make -C sound modules
> make[2]: Entering directory `/home/alastair/linux-2.4/drivers/sound'
> gcc -D__KERNEL__ -I/home/alastair/linux-2.4/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
> -DMODULE -DMODVERSIONS -include
> /home/alastair/linux-2.4/include/linux/modversions.h -nostdinc -I
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/include
> -DKBUILD_BASENAME=opl3sa2 -c -o opl3sa2.o opl3sa2.copl3sa2.c: In
> function `probe_opl3sa2':
> opl3sa2.c:721: structure has no member named `iobase'
> opl3sa2.c: At top level:
> opl3sa2.c:347: warning: `opl3sa2_mixer_restore' defined but not used
> make[2]: *** [opl3sa2.o] Error 1
> make[2]: Leaving directory `/home/alastair/linux-2.4/drivers/sound'
> make[1]: *** [_modsubdir_sound] Error 2
> make[1]: Leaving directory `/home/alastair/linux-2.4/drivers'
> make: *** [_mod_drivers] Error 2
>
> Cheers
> Alastair
>
> o o o o o o o o o o o o o o o o o o o o o o o o o o o o
> Alastair Stevens \ \
> MRC Biostatistics Unit \ \___________ 01223 330383
> Cambridge UK \___ www.mrc-bsu.cam.ac.uk
>
> -
> 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/
--
"hello it's not like i read my mail so that you have where to offer to sell me
a giant turnip or anything else thankyou." -tomas szepe <kala@pinerecords.com>
next prev parent reply other threads:[~2002-04-29 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 12:38 Compile failure: 2.4.19-pre7-ac3 Alastair Stevens
2002-04-29 14:40 ` tomas szepe [this message]
2002-04-29 14:55 ` tomas szepe
-- strict thread matches above, loose matches on Subject: below --
2002-04-29 13:34 Rudmer van Dijk
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=20020429144012.GC24016@louise.pinerecords.com \
--to=kala@pinerecords.com \
--cc=alastair.stevens@mrc-bsu.cam.ac.uk \
--cc=linux-kernel@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