All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langer <martin-langer@gmx.de>
To: Panagiotis Papadakos <papadako@csd.uoc.gr>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Problem compiling latest CVS with gcc-2.95.3
Date: Sat, 8 Mar 2003 10:11:24 +0100	[thread overview]
Message-ID: <20030308091124.GA29733@tuba.home> (raw)
In-Reply-To: <Pine.GSO.4.53.0303081049350.29156@oneiro.csd.uch.gr>

On Sat, Mar 08, 2003 at 10:51:29AM +0200, Panagiotis Papadakos wrote:
> I get the following error:

same with gcc 2.95.4!

martin


> 
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/mnt/disk/CVS/ALSA-CVS/alsa-driver/include
> -I/lib/modules/2.4.21-pre5-ac2/build/include -O2
> -mpreferred-stack-boundary=2 -march=i686 -falign-functions=4 -DLINUX -Wall
                                           ^^^^^^^^^^^^^^^^^^^
> -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2
> -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD  usbaudio.c usbmidi.c
> usbmixer.c > .depend
> make[1]: Leaving directory `/mnt/disk/CVS/ALSA-CVS/alsa-driver/usb'
> make[1]: Entering directory `/mnt/disk/CVS/ALSA-CVS/alsa-driver/acore'
> gcc -D__KERNEL__ -DMODULE=1 -I/mnt/disk/CVS/ALSA-CVS/alsa-driver/include
> -I/lib/modules/2.4.21-pre5-ac2/build/include -O2
> -mpreferred-stack-boundary=2 -march=i686 -falign-functions=4 -DLINUX -Wall
> -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2
> -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD   -DEXPORT_SYMTAB -c
> hwdep.c
> cc1: Invalid option `-falign-functions=4'
                       ^^^^^^^^^^^^^^^^^^^
> make[1]: *** [hwdep.o] Error 1
> make[1]: Leaving directory `/mnt/disk/CVS/ALSA-CVS/alsa-driver/acore'
> make: *** [compile] Error 1
> -(root@Santorini:0)-(12 files:18k@ALSA-CVS)-(0 jobs)-(10:48)-
> -(/mnt/disk/CVS/ALSA-CVS:#)->


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

  reply	other threads:[~2003-03-08  9:11 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 [this message]
2003-03-08  9:40   ` Martin Langer
2003-03-08 22:44     ` Martin Langer
2003-03-11 10:14       ` Takashi Iwai
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=20030308091124.GA29733@tuba.home \
    --to=martin-langer@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --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.