| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20070416174605.98260DBA1@gherkin.frus.com> Date: Mon, 16 Apr 2007 12:46:05 -0500 (CDT) From: rct@...rkin.frus.com (Bob Tracy) To: linux-kernel@...r.kernel.org Subject: [BUG] aic7xxx/aicasm build failure w/gcc-3.4.6 This showed up during a 2.6.21-rc7 build after I upgraded gcc from 3.3 to 3.4 on a Slackware system: make -C drivers/scsi/aic7xxx/aicasm (...) gcc -I/usr/include -I. aicasm.c aicasm_symbol.c aicasm_gram.c aicasm_macro_gram.c aicasm_scan.c aicasm_macro_scan.c -o aicasm -ldb aicasm_gram.y:1948: error: conflicting types for 'yyerror' aicasm_gram.tab.c:3004: error: previous implicit declaration of 'yyerror' was here aicasm_macro_gram.y:162: error: conflicting types for 'mmerror' aicasm_macro_gram.tab.c:1196: error: previous implicit declaration of 'mmerror' was here As a workaround, deleting the "void" declarations for yyerror() and mmerror() in the respective ".y" files fixes the problem. Here's the "gcc -v" output: Reading specs from /usr/lib/gcc/i486-slackware-linux/3.4.6/specs Configured with: ../gcc-3.4.6/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.4.6 -- ----------------------------------------------------------------------- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org rct@...s.com ----------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists