From: Takashi Iwai <tiwai@suse.de>
To: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: minor bug in make-install target
Date: Mon, 11 Feb 2002 12:03:42 +0100 [thread overview]
Message-ID: <s5hwuxkxott.wl@alsa2.suse.de> (raw)
In-Reply-To: <3C666090.52D64A93@folkwang-hochschule.de>
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/<version>/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..
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-02-11 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C591414.4FFDF135@folkwang-hochschule.de>
[not found] ` <s5h3d0mzemh.wl@alsa1.suse.de>
2002-02-10 11:59 ` minor bug in make-install target Jörn Nettingsmeier
2002-02-11 11:03 ` Takashi Iwai [this message]
2002-02-11 14:27 ` Jörn Nettingsmeier
2002-02-11 15:06 ` Takashi Iwai
2002-02-12 20:07 ` FIXED: " Jörn Nettingsmeier
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=s5hwuxkxott.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=nettings@folkwang-hochschule.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