From: =?iso-8859-1?Q?J=F6rn?= Nettingsmeier Subject: Re: minor bug in make-install target Date: Mon, 11 Feb 2002 15:27:11 +0100 Message-ID: <3C67D4BF.C3ECFA56@folkwang-hochschule.de> References: <3C591414.4FFDF135@folkwang-hochschule.de> <3C666090.52D64A93@folkwang-hochschule.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Takashi Iwai Cc: "alsa-devel@lists.sourceforge.net" List-Id: alsa-devel@alsa-project.org Takashi Iwai wrote: > > At Sun, 10 Feb 2002 12:59:12 +0100, > Jörn Nettingsmeier wrote: > > > > Takashi Iwai wrote: > > > > > > Hi, > > > > > > At Thu, 31 Jan 2002 10:53:24 +0100, > > > Jörn Nettingsmeier wrote: > > > > > > > > hello jaroslav ! > > > > > > > > i just found a minor bug in the make install target of alsa-driver: > > > > > > > > on my system, /usr/src is a link to /data1/src (which is another > > > > disk). > > > > > > > > i have alsa sources on /usr/src/alsa-cvs/alsa-driver > > > > > > > > when i "make install" the kernel modules, i end up with > > > > /lib/modules//kernel/sound/data1/src/alsa-cvs/alsa-driver/{acore,pci,synth} > > > > > > > > is it possible to fix the script so that it uses the correct paths > > > > even when it's a link ? > > > > > > > > btw, i also tried a relative link (src -> ../data/src), but the > > > > problem remains. > > > > > > > > moving the module tree by hand works for me, and it might not be > > > > worth fixing when the stuff goes into the kernel anyway, but i > > > > thought you might want to know. > > > > > > I fixed on cvs. > > > > > > now Rules.make guesses the destination directory from TREETOPDIR > > > variable, which is exported from the toplevel Makefile, so that TOPDIR > > > defined in each sub directory doesn't matter. > > > > > > this mechanism seems working at least on my system. > > > please give a try. > > > > hi takashi ! > > > > sorry for the long delay. i have just checked out alsa-cvs again, > > and the problem remains. > > i still get > > /lib/modules/2.4.18-pre9/kernel/sound/data1/src/alsa-cvs/alsa-driver/{pci,acore,synth} > > please check whether your MAINSRCDIR is defined in Makefile.conf > correctly, in your case, /data1/src/alsa-cvs/alsa-driver. > the latest Rules.make reduces the path name according to this > variable. it's possbile that the path name is different due to > symlinks.. i have mainsrcdir = . MAINSRCDIR = /usr/src/alsa-cvs/alsa-driver that's probably because i go to that directory via cd /usr/src/alsa-cvs/alsa-driver. how come the makefile ever knows we are in /data1/src ? pwd reports /usr/... if the makefile were just dumb enough, it would never even realize the symlink. but where does this extra piece of intelligence creep in ? i would expect the following behaviour: cd /usr/src/alsa-cvs/alsadriver => MAINSRCDIR = /usr/src/alsa-cvs/alsa-driver or cd /data1/src/alsa-cvs/alsadriver => MAINSRCDIR = /data1/src/alsa-cvs/alsa-driver in either case, all it has to do is cd MAINSRCDIR; cp -R pci acore synth /lib/modules/some-uname-magic/kernel/sound thanks for your help so far, regards, jörn -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.491621 http://spunk.dnsalias.org http://www.linuxdj.com/audio/lad/ _______________________________________________ Alsa-devel mailing list Alsa-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-devel