From: Andre Naujoks <nautsch2@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Cc: socketcan@hartkopp.net
Subject: Re: [PATCH] do not use --symlink for autoreconf
Date: Wed, 02 Jul 2014 14:34:42 +0200 [thread overview]
Message-ID: <53B3FC62.1030209@gmail.com> (raw)
In-Reply-To: <53B3F88E.2080202@pengutronix.de>
On 02.07.2014 14:18, Marc Kleine-Budde wrote:
> On 07/02/2014 02:12 PM, Andre Naujoks wrote:
>> When packaging the can-utils, I understand, that the generation
>> step for autoconf should be done beforehand. However using the
>> --symlink option in the autoreconf step installs links instead of
>> the actual files, which leads to a build failure when trying to
>> build on another host with different autotools installed.
>>
>> Signed-off-by: Andre Naujoks <nautsch2@gmail.com>
>
> How do you package the can-utils? The usual steps are:
>
> ./autogen.sh ./configure make dist
with git archive. Something like
git archive --prefix=can-utils-`git describe --always --dirty`/ -o
can-utils-`git describe --always --dirty`.tar.gz HEAD
I was not aware of the dist target. Why do I have to configure before
creating the dist? Isn't the configure step just for adaptations for
the build-host and target?
Andre
>
> Marc
>
next prev parent reply other threads:[~2014-07-02 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 12:12 [PATCH] do not use --symlink for autoreconf Andre Naujoks
2014-07-02 12:18 ` Marc Kleine-Budde
2014-07-02 12:34 ` Andre Naujoks [this message]
2014-07-02 12:41 ` Andre Naujoks
2014-07-02 12:58 ` Marc Kleine-Budde
2014-07-02 13:06 ` Marc Kleine-Budde
2014-07-02 13:07 ` Marc Kleine-Budde
2014-07-02 13:08 ` Marc Kleine-Budde
2014-07-02 13:47 ` Andre Naujoks
2014-07-02 14:05 ` Marc Kleine-Budde
2014-07-02 14:09 ` Andre Naujoks
2014-07-02 12:57 ` 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=53B3FC62.1030209@gmail.com \
--to=nautsch2@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
/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.