all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 40604-done@debbugs.gnu.org
Subject: bug#40604: http-parser 2.9.4 fails to build on armhf-linux
Date: Thu, 21 May 2020 22:07:41 +0200	[thread overview]
Message-ID: <875zcpdpbm.fsf@elephly.net> (raw)
In-Reply-To: <87o8qhpcry.fsf@nckx>


Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Ricardo, Marius,
>
> Ricardo Wurmus 写道:
>>> Marius Bakke <mbakke@fastmail.com> writes:
>>>
>>>> The update to http-parser in
>>>> 62f7f0d636d3b3ff796263ab892ebf53263539fa
>>>> causes a test failure armhf-linux:
>>>
>>> The same test failure happens on i686-linux.
>>
>> Actually, this might be a different failure:
>>
>>     test_g: test.c:4240: main: Assertion `sizeof(http_parser) ==
>> 32' failed.
>
> Neither, or both, or whatever.  It's the fix for the armhf failure
> (5c30eb61) that in turn causes a failure on i686 because there the
> struct *is* a mere 28 bytes.
>
> Fixed in f2de892b375d30ad79502509a47a15f0f4d68fee by applying the fix
> only on armhf.

Thank you!  That got me past “guix pull” on my i686-linux netbook.

-- 
Ricardo




      reply	other threads:[~2020-05-21 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 18:16 bug#40604: http-parser 2.9.4 fails to build on armhf-linux Marius Bakke
2020-04-13 18:25 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-21 10:53 ` Ricardo Wurmus
2020-05-21 10:54   ` Ricardo Wurmus
2020-05-21 14:45     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-21 20:07       ` Ricardo Wurmus [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=875zcpdpbm.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=40604-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.