From: Leo Famulari <leo@famulari.name>
To: Sergei Trofimovich <slyfox@inbox.ru>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: packages: flex: Add missing 'lzip' input.
Date: Sun, 28 May 2017 14:50:22 -0400 [thread overview]
Message-ID: <20170528185022.GE15883@jasmine> (raw)
In-Reply-To: <20170528183702.28f9c419@sf>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Sun, May 28, 2017 at 06:37:02PM +0100, Sergei Trofimovich wrote:
> > On Sun, May 28, 2017 at 02:51:10PM +0200, Ludovic Courtès wrote:
> > > leo@famulari.name (Leo Famulari) skribis:
> > > > gnu: packages: flex: Add missing 'lzip' input.
> > > >
> > > > * gnu/packages/flex.scm (flex)[native-inputs]: Add lzip.
> > >
> > > I think this breaks ‘flex-boot0’ in (gnu packages commencement), doesn’t
> > > it?
>
> Can you clarify a bit what exactly broke here? Is it bootstrap on hurd?
> guix seemed to build things fine here on linux.
See the flex-boot0 package in 'gnu/packages/commencement.scm. This
package inherits from flex but limits the native-inputs to bison-boot0
and %boot0-inputs. So, lzip is not available here.
Although I didn't try building it from the lzip-compressed tarball, I
expect flex-boot0 would fail to build unless we added lzip to its
native-inputs. Did work for you?
> I don't understand how flex could work before the patch as lzip was not
> pulled in as a dependency and the tarball is clearly an .lz one.
Right, since commit 93fabf59962aeb15981bd547850de1dab69eccfb (gnu: flex:
Update to 2.6.4.) the flex package was broken. We didn't notice right
away because it was on core-updates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-05-28 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170527140816.860.97229@vcs0.savannah.gnu.org>
[not found] ` <20170527140817.A6C6B2052F@vcs0.savannah.gnu.org>
2017-05-28 12:51 ` 01/01: gnu: packages: flex: Add missing 'lzip' input Ludovic Courtès
2017-05-28 13:58 ` Leo Famulari
2017-05-28 17:37 ` Sergei Trofimovich
2017-05-28 18:50 ` Leo Famulari [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=20170528185022.GE15883@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=slyfox@inbox.ru \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.