From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Théo Lebrun" <theo.lebrun@bootlin.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/ragel: new package
Date: Wed, 20 Apr 2022 23:07:14 +0200 [thread overview]
Message-ID: <20220420210714.GJ2730@scaer> (raw)
In-Reply-To: <20220420205708.GI2730@scaer>
Théo, All,
On 2022-04-20 22:57 +0200, Yann E. MORIN spake thusly:
> On 2022-03-10 16:20 +0100, Théo Lebrun via buildroot spake thusly:
> > This is an host-only package that does preprocessing to .rl files to
> > turn them into .c or .cpp files.
[--SNIP--]
> > +RAGEL_VERSION = 6.10
> > +RAGEL_SITE = https://www.colm.net/files/ragel/
> > +RAGEL_LICENSE = GPL-2.0
> > +RAGEL_LICENSE_FILES = COPYING
> > +RAGEL_CONF_OPTS = \
> > + --disable-silent-rules \
> > + --disable-manual \
> > + --disable-dependency-tracking
Gah, I forgot to comment about those before pushing and sending the
previous mail...
So, why were --disable-silent-rules and --disable-dependency-tracking
needed? Usually, they are not needed, and we do not even set them in our
autotools-package infra.
If they are really important, could you please send a followup that adds
a comment above RAGEL_CONF_OPTS? And if they are not needed, can you
send a followup patch that removes them?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-04-20 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 15:20 [Buildroot] [PATCH 1/3] package/ragel: new package Théo Lebrun via buildroot
2022-03-10 15:20 ` [Buildroot] [PATCH 2/3] package/roc: " Théo Lebrun via buildroot
2022-04-20 21:28 ` Yann E. MORIN
2022-03-10 15:20 ` [Buildroot] [PATCH 3/3] package/pipewire: add optional roc Théo Lebrun via buildroot
2022-04-20 20:57 ` [Buildroot] [PATCH 1/3] package/ragel: new package Yann E. MORIN
2022-04-20 21:07 ` Yann E. MORIN [this message]
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=20220420210714.GJ2730@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/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.