From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] moving package divine from autotools-package to generic-package
Date: Sat, 9 Mar 2013 10:13:25 +0100 [thread overview]
Message-ID: <20130309101325.7b8352e8@skate> (raw)
In-Reply-To: <513A5360.8080707@googlemail.com>
Dear Carsten Schoenert,
On Fri, 08 Mar 2013 22:08:48 +0100, Carsten Schoenert wrote:
> But, the archive on directfb.org is broken, inside the archive in the
> lib/ directory the Header idivine.h is missing. Inside the Git Repo
> everything is fine. I wrote up the maintainer and describe the issue but
> until now no response from there.
> So I tried to change package divine from a autotools-package to a
> generic package because the Git Repo just shipped a file autogen.sh for
> package preparation.
No, no, it should continue to be an autotools-package. It has a
configure.in, and Makefile.am, it is autotools based, so it should
remain an autotools-package.
Now, since you're getting it from git instead of a tarball, the
configure script and Makefile.in are not pre-generated, so we have to
get them generated.
Can you just try to do:
DIVINE_AUTORECONF = YES
in the package recipe?
Looking at what the autogen.sh script does, I think our autoreconf
logic should work. Otherwise, we will just add a hook in the package
recipe in order to call autogen.
But clearly, converting to generic-package is the wrong way to go.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-09 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 21:08 [Buildroot] moving package divine from autotools-package to generic-package Carsten Schoenert
2013-03-09 9:13 ` Thomas Petazzoni [this message]
2013-03-10 8:59 ` Carsten Schoenert
2013-03-10 9:27 ` Thomas Petazzoni
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=20130309101325.7b8352e8@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox