From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ngrep: bump to version 1.47
Date: Sun, 04 Nov 2018 13:34:10 +0200 [thread overview]
Message-ID: <87lg69nkjx.fsf@tkos.co.il> (raw)
In-Reply-To: <CAPi7W83CQfQGjuhZBUvZoPBsJJLSE2sgRj_P9UHt7Lvb9bpqpA@mail.gmail.com>
Hi Fabric,
Fabrice Fontaine writes:
> Dear Thomas,
> Le dim. 4 nov. 2018 ? 11:19, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> a ?crit :
>>
>> Hello,
>>
>> On Sat, 3 Nov 2018 23:01:07 +0100, Fabrice Fontaine wrote:
>>
>> > > So PCRE is not mandatory.
>> > Indeed, PCRE is not really "mandatory", ngrep use GNU regex by default
>> > but this was already the case before the bump (in version 1.45): see
>> > https://github.com/jpr5/ngrep/blob/V1_45/configure.in.
>> > I didn't want to change this behavior when bumping the package and I
>> > could find why pcre wasn't made optional in the initial commit back in
>> > 2011.
>> > However, I'll add a third patch in my serie to make pcre an optional
>> > dependency before bumping the package..
>>
>> Indeed, it could be a third patch.
> OK, when I tried to enable GNU regex (on 1.47), I got the following error:
> /usr/bin/make w -j --jobserver-fds=3,4 -C regex-0.12 regex.o
> make[2]: Entering directory
> '/home/fabrice/buildroot/output/build/ngrep-1_47/regex-0.12'
> make[2]: *** No rule to make target 'w'. Stop.
>
> This error is raised by this command:
> $(MAKE) $(MAKEFLAGS) -C $(REGEX_DIR) $(notdir $(REGEX_OBJS))
>
> which means that MAKEFLAGS is set to "w -j --jobserver-fds=3,4".
> I don't understand where this "w" and not "-w" is coming from. Do you
> have any advice or clue?
This is most likely related to mismatch of make versions being used when
we build our own host-make. See the discussion in this thread related to
boa:
http://lists.busybox.net/pipermail/buildroot/2018-October/232957.html
There is no fix to this issue yet.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-11-04 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:23 [Buildroot] [PATCH 1/2] ngrep: bump to version 1.47 Fabrice Fontaine
2018-11-01 13:23 ` [Buildroot] [PATCH 2/2] ngrep: add libnet optional dependency Fabrice Fontaine
2018-11-03 21:42 ` [Buildroot] [PATCH 1/2] ngrep: bump to version 1.47 Thomas Petazzoni
2018-11-03 22:01 ` Fabrice Fontaine
2018-11-04 10:19 ` Thomas Petazzoni
2018-11-04 11:04 ` Fabrice Fontaine
2018-11-04 11:28 ` Thomas Petazzoni
2018-11-04 11:34 ` Baruch Siach [this message]
2018-11-06 0:14 ` Arnout Vandecappelle
2018-11-06 7:59 ` Thomas Petazzoni
2018-11-06 9:54 ` Peter Korsgaard
2018-11-06 10:31 ` Arnout Vandecappelle
2018-11-06 11:18 ` 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=87lg69nkjx.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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 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.