From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnuplot : new package
Date: Fri, 4 Jan 2013 19:02:19 +0100 [thread overview]
Message-ID: <20130104190219.2ff62738@skate> (raw)
In-Reply-To: <50E714EF.4090102@relinux.de>
Dear Stephan Hoffmann,
On Fri, 04 Jan 2013 18:44:15 +0100, Stephan Hoffmann wrote:
> maybe my question was not clear enough. I just wanted to know if this
> option is really required.
> > Instead, we prefer having small packages that only support the features
> > that have been tested by the submitter, and that carefully disables all
> > the unsupported features. And then, as features are needed by other
> > people, they can submit additional patches to make those additional
> > features work.
> O.K., I didn't realize that even when configure finds out that no X11 is
> present --without-x is needed for this reason.
>
> For the records: I made a quick test without X11 and it fails to compile
> without this option.
Generally, it's quite good to have explicit --disable-<feature> or
--without-<feature>. It avoids the configure script from
potentially mis-detecting host libraries. Like gnuplot configure script
could say "hey, your build machine has X, let's build X support".
Passing --without-x avoids that.
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-01-04 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:53 [Buildroot] [PATCH] gnuplot : new package Anthony Viallard
2013-01-04 15:15 ` Thomas Petazzoni
2013-01-04 15:38 ` Viallard Anthony
2013-01-04 15:32 ` Stephan Hoffmann
2013-01-04 16:26 ` Thomas Petazzoni
2013-01-04 17:44 ` Stephan Hoffmann
2013-01-04 18:02 ` Thomas Petazzoni [this message]
2013-01-04 18:01 ` Stephan Hoffmann
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=20130104190219.2ff62738@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