From: Alexander GQ Gerasiov <gq@cs.msu.su>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Nikita <nebaruzdin@lvk.cs.msu.su>
Subject: Re: can-utils: install in /usr/bin instead of /usr/local/bin ??
Date: Fri, 24 Jan 2014 01:46:33 +0400 [thread overview]
Message-ID: <20140124014633.58e1b389@snail> (raw)
In-Reply-To: <52E17C7A.5070209@pengutronix.de>
Thu, 23 Jan 2014 21:32:58 +0100
Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> > So I use plain Makefile in my not-yet-uploaded-into-Debian package.
> >
> > If you want to get rid of it, I'd recommend you remove it completely
> > from git, rename auto* to common name (for now Makefile called
> > GNUmakefile or something like that) and remove from git any
> > autogenerated files.
>
> From the GNU make info page:
> ""By default, when `make' looks for the makefile, it tries the
> following names, in order: `GNUmakefile', `makefile' and `Makefile'.""
>
> So GNUmakefile has a higher priority as Makefile.
Oh, didn't knew that. Ok.
> There aren't any auto generated files in the git.
Really strange, just tried to reproduce this and didn't find any
problems. May be I confuse can-utils with another code, I packaged on
the holiday, dont know =\
> Just call:
>
> ./autogen.sh
> ./configure
> make
In my case there will be just
#!/usr/bin/make -f
%:
dh $@ --with autoreconf
in debian/rules :)
next prev parent reply other threads:[~2014-01-23 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 13:58 can-utils: install in /usr/bin instead of /usr/local/bin ?? Oliver Hartkopp
2014-01-23 14:00 ` Marc Kleine-Budde
2014-01-23 14:07 ` Yegor Yefremov
2014-01-23 14:12 ` Marc Kleine-Budde
2014-01-23 16:26 ` Alexander GQ Gerasiov
2014-01-23 20:32 ` Marc Kleine-Budde
2014-01-23 21:46 ` Alexander GQ Gerasiov [this message]
2014-01-23 21:49 ` Marc Kleine-Budde
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=20140124014633.58e1b389@snail \
--to=gq@cs.msu.su \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=nebaruzdin@lvk.cs.msu.su \
--cc=socketcan@hartkopp.net \
--cc=yegorslists@googlemail.com \
/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.