From: Matthias Schwarzott <zzam@gentoo.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org, Trent Piepho <xyzzy@speakeasy.org>,
Andy Walls <awalls@radix.net>
Subject: Re: lsmod path hardcoded in v4l/Makefile
Date: Tue, 21 Jul 2009 09:14:36 +0200 [thread overview]
Message-ID: <200907210914.37819.zzam@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0906231214360.6411@shell2.speakeasy.net>
On Dienstag, 23. Juni 2009, Trent Piepho wrote:
> On Tue, 23 Jun 2009, Matthias Schwarzott wrote:
> > > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote:
> > > > It seems the path to lsmod tool is hardcoded in the Makefile for
> > > > out-of-tree building of v4l-dvb.
> >
> > Shouldn't $PATH of root be considered safe? Else the distro or the system
>
> I believe make will set the variable whenever the makefile is used, even
> when building as non-root.
>
> It turns out that it was just lsmod with no path originally, but Michael
> Krufky changed it back in 2005 (commit b0e7b40744ef) to have a hardcoded
> path. Then later in commit c91e7f84a1d6 the only use of 'v4l_modules' was
> deleted, so we can just delete this line and not worry about sbin and
> paths.
>
> Mauro,
>
> Please pull from http://linuxtv.org/hg/~tap/fix
>
> for the following changeset:
>
> build: Remove module list cruft
> http://linuxtv.org/hg/~tap/fix?cmd=changeset;node=fb228bb1ad9f
Hi Mauro!
is there any reason to not pull this besides time?
Regards
Matthias
next prev parent reply other threads:[~2009-07-21 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 14:36 lsmod path hardcoded in v4l/Makefile Matthias Schwarzott
2009-06-22 22:42 ` Andy Walls
2009-06-22 23:01 ` Trent Piepho
2009-06-23 7:51 ` Matthias Schwarzott
2009-06-22 23:39 ` Theodore Kilgore
2009-06-23 8:24 ` Matthias Schwarzott
2009-06-23 7:50 ` Matthias Schwarzott
2009-06-23 19:29 ` Trent Piepho
2009-07-21 7:14 ` Matthias Schwarzott [this message]
2009-07-28 1:07 ` Mauro Carvalho Chehab
2009-07-28 7:30 ` Trent Piepho
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=200907210914.37819.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=awalls@radix.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=xyzzy@speakeasy.org \
/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