unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>, julien lepiller <roptat@lepiller.eu>
Subject: Re: Fixing ant-bootstrap / jamvm segfault (i686)
Date: Fri, 27 Sep 2019 09:13:26 +0200	[thread overview]
Message-ID: <87blv6gqjt.fsf@elephly.net> (raw)
In-Reply-To: <CAE4v=ph7dsZsz1P_B+S93=hZLvLLFa1JOGFuAM0U-b3kXdVJvg@mail.gmail.com>


Hi Gábor,

> Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2019. szept. 16.,
> Hét 15:20):
>
>> Hi Guix,
>>
>> here’s a probably needlessly complicated patch to fix the build of
>> ant-bootstrap.  It currently fails to build because jamvm
>> segfaults.

[…]

>> I’m almost certain that not all of these configure flags are needed.
>> What do you think?  Would someone like to play a little with this patch
>> and see if we can figure out why exactly jamvm segfaults?
>>
> I will try to have a look at this again in the coming days.
>
>>
>> I used this command to build ant-bootstrap:
>>
>>     ./pre-inst-env guix build -K --system=i686-linux -e '(@@ (gnu packages
>> java) ant-bootstrap)'

Have you been able to take a look at this?  I’d like to push this or a variant
of it to the core-updates branch soon.

-- 
Ricardo

  reply	other threads:[~2019-09-27  7:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 13:20 Fixing ant-bootstrap / jamvm segfault (i686) Ricardo Wurmus
2019-09-16 14:42 ` Gábor Boskovits
2019-09-27  7:13   ` Ricardo Wurmus [this message]
2019-09-27  7:41     ` Gábor Boskovits
2019-09-27  7:52       ` Ricardo Wurmus
2019-09-28 21:14         ` Gábor Boskovits
2019-09-28 21:49           ` Gábor Boskovits
2019-09-30 19:59             ` Ricardo Wurmus
2019-10-01  1:01               ` Ricardo Wurmus
2019-10-01  5:46                 ` Gábor Boskovits

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blv6gqjt.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=roptat@lepiller.eu \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).