From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package: indentation cleanup
Date: Thu, 15 Jan 2015 09:43:14 +0100 [thread overview]
Message-ID: <20150115094314.59c5175f@free-electrons.com> (raw)
In-Reply-To: <1421306499-16540-1-git-send-email-jerzy.grzegorek@trzebnica.net>
Dear Jerzy Grzegorek,
Thanks, I've applied, but there are a few questions that come to mind
when looking at the patch.
On Thu, 15 Jan 2015 08:21:39 +0100, Jerzy Grzegorek wrote:
> +JIMTCL_INSTALL_LIB = \
> + $(INSTALL) -D $(@D)/libjim.$(JIMTCL_LIB) \
> + $(TARGET_DIR)/usr/lib/libjim.$(JIMTCL_LIB); \
> + ln -s libjim.$(JIMTCL_LIB) $(TARGET_DIR)/usr/lib/libjim.so
We should be using a "define ... endef" block here:
define JIMTCL_INSTALL_LIB
...
...
...
endef
This would remove the need for the backslashes, and make it more
similar to what we do in the rest of Buildroot.
> diff --git a/package/xerces/xerces.mk b/package/xerces/xerces.mk
> index 9b2bb81..59b8d8a 100644
> --- a/package/xerces/xerces.mk
> +++ b/package/xerces/xerces.mk
> @@ -11,8 +11,9 @@ XERCES_LICENSE = Apache-2.0
> XERCES_LICENSE_FILES = LICENSE
> XERCES_MAKE = $(MAKE1)
> XERCES_INSTALL_STAGING = YES
> -XERCES_CONF_OPTS = --disable-threads \
> - --with-gnu-ld
> +XERCES_CONF_OPTS = \
> + --disable-threads \
Why are we disabling threads unconditionally here?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-15 8:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 7:21 [Buildroot] [PATCH 1/1] package: indentation cleanup Jerzy Grzegorek
2015-01-15 8:43 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-22 6:38 Jerzy Grzegorek
2015-06-22 21:06 ` Peter Korsgaard
2015-06-18 6:10 Jerzy Grzegorek
2015-06-18 15:58 ` Arnout Vandecappelle
2015-06-18 21:42 ` Thomas Petazzoni
2014-12-30 7:36 Jerzy Grzegorek
2014-12-30 10:17 ` Peter Korsgaard
2014-12-24 7:54 Jerzy Grzegorek
2014-12-24 10:44 ` Thomas Petazzoni
2014-12-22 8:12 Jerzy Grzegorek
2014-12-22 8:28 ` Thomas Petazzoni
2014-12-15 8:56 Jerzy Grzegorek
2014-12-16 7:15 ` Thomas Petazzoni
2014-12-20 20:53 ` Thomas Petazzoni
2014-12-09 15:14 Jerzy Grzegorek
2014-12-10 20:54 ` Thomas Petazzoni
2014-10-27 8:25 Jerzy Grzegorek
2014-11-02 22:27 ` Peter Korsgaard
2014-10-25 18:29 Jerzy Grzegorek
2014-10-26 4:47 ` Peter Korsgaard
2014-10-25 6:20 Jerzy Grzegorek
2014-10-25 8:39 ` Thomas Petazzoni
2014-10-24 5:57 Jerzy Grzegorek
2014-10-24 23:15 ` Peter Korsgaard
2014-10-23 8:43 Jerzy Grzegorek
2014-10-23 20:14 ` Thomas Petazzoni
2014-10-02 20:04 Jerzy Grzegorek
2014-10-02 20:44 ` Peter Korsgaard
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=20150115094314.59c5175f@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