From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] dieharder: new package
Date: Sun, 17 May 2015 15:55:22 +0200 [thread overview]
Message-ID: <20150517155522.7b71a525@free-electrons.com> (raw)
In-Reply-To: <20150517121815.GA29019@vdg.name>
Dear Julien Viard de Galbert,
On Sun, 17 May 2015 14:18:15 +0200, Julien Viard de Galbert wrote:
> > Those help lines look fairly too long. Make sure they're not longer
> > than 72 columns.
> >
> Ok, also I just sent another patch to document that point.
Sure, good idea.
> You are right this should be made more explicit, there is an
> extra "beverage" clause in the licence file.
> I could either use the syntax the software uses:
> DIEHARDER_LICENSE = GPLv2b (b for beverage)
>
> Or make it simply:
> DIEHARDER_LICENSE = GPLv2 with beverage clause
>
> What do you think ?
The second solution you propose looks better to me.
> > > +DIEHARDER_LICENSE_FILES = $(DIEHARDER_SUBDIR)/COPYING
> > > +DIEHARDER_DEPENDENCIES = gsl
> > > +
> > > +DIEHARDER_CONF_OPTS = --includedir=$(STAGING_DIR)/usr/include
> >
> > Why do you need this? This looks wrong, as it would install the
> > headers in a completely wrong location, if dieharder would be
> > installing headers. --includedir is not used to specify where a program
> > should look for headers of libraries, but to tell where it should
> > install its own headers.
> >
> That was to try to fix the build using "/usr/include/" but it's wrong.
> I overlooked the normal --includedir function. So I guess the upstream
> scripts are wrong as they use the --includedir value to also specify
> some include search path...
>
> Also it _really_ do install some headers there. We probably don't want
> those on the target rootfs. So I guess I need to find how to tell it not
> to do that...
As long as headers are installed in $(TARGET_DIR)/usr/include, you
shouldn't do anything: Buildroot automatically deletes this directory
at the end of the build process.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-17 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 7:43 [Buildroot] [PATCH v3] dieharder: new package julien.viarddegalbert at openwide.fr
2015-05-17 8:20 ` Thomas Petazzoni
2015-05-17 12:18 ` Julien Viard de Galbert
2015-05-17 13:55 ` Thomas Petazzoni [this message]
2015-07-10 23:10 ` Romain Naour
2015-07-11 7:43 ` Yann E. MORIN
2015-07-15 7:43 ` Julien Viard de Galbert
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=20150517155522.7b71a525@free-electrons.com \
--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