From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>, julien lepiller <roptat@lepiller.eu>
Subject: Re: Fixing ant-bootstrap / jamvm segfault (i686)
Date: Sat, 28 Sep 2019 23:14:13 +0200 [thread overview]
Message-ID: <CAE4v=pjiwG8+D0EJo8G3aSSudzHnW-bhXzoSq5v6fbxU4qO7-g@mail.gmail.com> (raw)
In-Reply-To: <87a7aqgorh.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
Hello,
Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2019. szept. 27., P,
9:52):
>
> Gábor Boskovits <boskovits@gmail.com> writes:
>
> > Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2019. szept. 27.,
> > Pén 9:14):
> >
> >>
> >> 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.
> >>
> > Not yet. I will have a look tomorrow and report back if that is not too
> > late.
>
> Tomorrow would be just fine. There’s no real rush, but I’d like to
> avoid forgetting about this when we already have the means to fix lots
> of broken packages on core-updates.
>
> Thanks for taking a look at this!
>
> --
> Ricardo
>
>
So far I can confirm that the patch as is works fine for me. I will now
have a look at reducing this.
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
[-- Attachment #2: Type: text/html, Size: 2801 bytes --]
next prev parent reply other threads:[~2019-09-28 21:14 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
2019-09-27 7:41 ` Gábor Boskovits
2019-09-27 7:52 ` Ricardo Wurmus
2019-09-28 21:14 ` Gábor Boskovits [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pjiwG8+D0EJo8G3aSSudzHnW-bhXzoSq5v6fbxU4qO7-g@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--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 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.