From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: papadako@csd.uoc.gr, alsa-devel@lists.sourceforge.net
Subject: Re: Problem compiling latest CVS with gcc-2.95.3
Date: Tue, 11 Mar 2003 11:14:43 +0100 [thread overview]
Message-ID: <s5hu1ea2orw.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030308224427.GA25823@tuba.home>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
At Sat, 8 Mar 2003 23:44:27 +0100,
Martin Langer wrote:
>
> On Sat, Mar 08, 2003 at 10:40:52AM +0100, Martin Langer wrote:
> > On Sat, Mar 08, 2003 at 10:11:24AM +0100, Martin Langer wrote:
> > > On Sat, Mar 08, 2003 at 10:51:29AM +0200, Panagiotis Papadakos wrote:
> > >
> > > > cc1: Invalid option `-falign-functions=4'
>
>
> Removing that option really helps in my case. Don't know if it should be
> really applied to the CVS tree.
IIRC, the -falign-xxx is a new option and the older compiler had
-malign-xxx instead. could you check the attached patch whether it
works?
Takashi
[-- Attachment #2: config-fix.dif --]
[-- Type: application/octet-stream, Size: 1828 bytes --]
Index: alsa-driver/configure.in
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-driver/configure.in,v
retrieving revision 1.99
diff -u -r1.99 configure.in
--- alsa-driver/configure.in 10 Mar 2003 13:02:39 -0000 1.99
+++ alsa-driver/configure.in 10 Mar 2003 16:29:24 -0000
@@ -335,8 +335,7 @@
fprintf(file, "i386");
#elif defined(CONFIG_M486)
fprintf(file, "i486");
-#elif defined(CONFIG_M586) || defined(CONFIG_MWINCHIPC6) || defined(CONFIG_MWINCHIP2)\
- || defined(CONFIG_MWINCHIP3D) || defined(CONFIG_MCYRIXIII)
+#elif defined(CONFIG_M586)
fprintf(file, "i586");
#elif defined(CONFIG_M586TSC)
fprintf(file, "i586tsc");
@@ -434,11 +433,19 @@
if $CC -march=athlon -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then
c_opts="-march=athlon"
else
- c_opts="-march=i686 -malign-functions=4"
+ if $CC -falign-functions=0 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then
+ c_opts="-march=i686 -falign-functions=4"
+ else
+ c_opts="-march=i686 -malign-functions=4"
+ fi
fi
;;
crusoe)
- c_opts="-march=i686 -malign-functions=0 -malign-jumps=0 -malign-loops=0"
+ if $CC -falign-functions=0 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then
+ c_opts="-march=i686 -falign-functions=0 -falign-jumps=0 -falign-loops=0"
+ else
+ c_opts="-march=i686 -malign-functions=0 -malign-jumps=0 -malign-loops=0"
+ fi
;;
mcyrixiii)
if $CC -march=c3 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then
@@ -573,7 +580,7 @@
dnl set ia32 (X86)
case "$processor" in
- i?86*|k?|crusoe)
+ i?86*|k?|crusoe|mcyrixiii|mwinchip)
if $CC -mpreferred-stack-boundary=2 -S -o /dev/null -xc /dev/null >/dev/null 2>&1; then
c_opts="-mpreferred-stack-boundary=2 $c_opts"
CONFIG_X86=y
next prev parent reply other threads:[~2003-03-11 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 8:51 Problem compiling latest CVS with gcc-2.95.3 Panagiotis Papadakos
2003-03-08 9:11 ` Martin Langer
2003-03-08 9:40 ` Martin Langer
2003-03-08 22:44 ` Martin Langer
2003-03-11 10:14 ` Takashi Iwai [this message]
2003-03-11 11:12 ` Martin Langer
2003-03-11 13:02 ` Takashi Iwai
2003-03-11 14:30 ` Martin Langer
2003-03-11 17:59 ` Takashi Iwai
2003-03-11 14:14 ` Panagiotis Papadakos
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=s5hu1ea2orw.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=martin-langer@gmx.de \
--cc=papadako@csd.uoc.gr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.