Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problems on alpha
Date: Mon, 17 Nov 2003 18:55:29 +0100	[thread overview]
Message-ID: <s5h65hikhgu.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hvfpjjlqg.wl@alsa2.suse.de>

At Mon, 17 Nov 2003 12:08:39 +0100,
I wrote:
> 
> At Sun, 16 Nov 2003 18:51:17 +0100,
> Martin Langer wrote:
> > 
> > 
> > Hi,
> > 
> > please don't try to build au88x0 on an alpha.
> 
> most of problems below are due to 2.2 kernel.
> the cvs version is not tested well on 2.2 kernels (also i tried only
> i386)
> 
> >  You have to read a lot. 
> > But here is an extract with some quite interesting points about CVS ;-)
> > 
> > martin
> > 
> > 
> > gcc -D__KERNEL__ -DMODULE=1 -I/usr/local/src/alsa-cvs/alsa-driver/include
> > -I/lib/modules/2.2.19/build/include -O2 -mno-fp-regs -ffixed-8 -Wa,-mev6
> > -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2
> > -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD
> > -DKBUILD_BASENAME=memory_wrapper   -c -o memory_wrapper.o memory_wrapper.c
> > memory_wrapper.c: In function snd_compat_vmalloc_to_page':
> > memory_wrapper.c:35: warning: implicit declaration of function VMALLOC_VMADDR'
> > memory_wrapper.c:39: warning: implicit declaration of function pgd_offset'
> > memory_wrapper.c:39: warning: assignment makes pointer from integer without
> > a cast
> > memory_wrapper.c:40: warning: implicit declaration of function pmd_offset'
> > memory_wrapper.c:40: warning: assignment makes pointer from integer without
> > a cast
> > memory_wrapper.c:41: warning: implicit declaration of function pte_offset'
> > memory_wrapper.c:41: warning: assignment makes pointer from integer without
> > a cast
> > memory_wrapper.c:43: warning: implicit declaration of function pte_page'
> 
> it seems that configure script didn't detect these checks correctly.
> could you check config.log ?

it seems that 2.2.19 kernel surely has these definitions.
are you sure that you pass the correct kernel source path to configure
script, or /lib/modules/2.2.19/build is symlinked to its kernel source
tree?


Takashi


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl

  reply	other threads:[~2003-11-17 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 17:51 problems on alpha Martin Langer
2003-11-17 11:08 ` Takashi Iwai
2003-11-17 17:55   ` Takashi Iwai [this message]
2003-11-17 21:15     ` Martin Langer
2003-11-17 21:26   ` Martin Langer
2003-11-18 10:09     ` Takashi Iwai
2003-11-23 14:27       ` Martin Langer

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=s5h65hikhgu.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=martin-langer@gmx.de \
    /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