public inbox for gentoo-musl@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-musl@lists.gentoo.org
Subject: Re: [gentoo-musl] Re: plan9port build fails on multiple levels.
Date: Fri, 30 Jun 2017 23:16:47 -0400	[thread overview]
Message-ID: <288f8497-48d6-49c6-aa65-f7c480dc2aba@gentoo.org> (raw)
In-Reply-To: <CAPmquXA_9UChm547fBLyA8ZoReoWX4xYXap11MkAHBE30fhjEg@mail.gmail.com>

On 6/30/17 5:14 PM, Rendov Norra wrote:
> I've attached the patches here, but I hesitate to present them as a
> solution since I'm incapable of testing them because of the segfaults
> I'm experiencing with egrep.
> 
> I'll also note that the version
> (e78ed7a67bbaa37dc57dfb37219f505c48755e14) is 3 years old. One big fix
> that happened since then is the change of some files' extensions for
> .C to .c, since they don't compile as .C .
> 
> As for why I'm interested in p9p, it's a feasible replacement base
> system in place of GNU--being small but still functional--, and sam
> and acme are useful editors.
> 
> On 6/30/17, Anthony G. Basile <basile@freeharbor.net> wrote:
>> On 6/30/17 3:02 AM, parazyd@dyne.org wrote:
>>> Do share them. plan9port doesn't compile on amd64 either.
>>>
>>> On Thu, 29 Jun 2017, Rendov Norra wrote:
>>>
>>>> I have patches to fix the first two issues (or at least they compile),
>>>> but they're very hacky as I'm not an experienced coder.
>>
>> Excellent, ignore my last message.  If you open a bug report at
>> bugs.gentoo.org, describe the problem and upload the patches and I'll
>> put it on the tree.  I also maintain plan9port so I can fix it directly.
>>
>> Having said that, I'm curious why people are interested in plan9port?
>>
>>>>
>>>> On 6/29/17, Rendov Norra <tsobf242@gmail.com> wrote:
>>>>> I should also note that this is on ARM
>>>>>
>>>>> On 6/29/17, Rendov Norra <tsobf242@gmail.com> wrote:
>>>>>> It fails at building its thread library, it fails at building
>>>>>> lib9/dirread, and I'm not sure if this is related at all but egrep
>>>>>> segfaults and kills the build.
>>>>>>
>>
>> --
>> Anthony G. Basile, Ph.D.
>> Gentoo Linux Developer [Hardened]
>> E-Mail    : basile@freeharbor.net
>> GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
>> GnuPG ID  : F52D4BBA
>>
>>
>>

I don't understand patch 2.  It eliminated an entire function which is
exposed for arm, so I don't see how that can be right.  Can you talk to
upstream about these.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA


  reply	other threads:[~2017-07-01  3:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  1:00 [gentoo-musl] plan9port build fails on multiple levels Rendov Norra
2017-06-30  1:01 ` [gentoo-musl] " Rendov Norra
2017-06-30  3:13   ` Rendov Norra
2017-06-30  7:02     ` parazyd
2017-06-30 13:10       ` Anthony G. Basile
2017-06-30 21:14         ` Rendov Norra
2017-07-01  3:16           ` Anthony G. Basile [this message]
2017-07-01 18:44             ` Rendov Norra
2017-06-30 13:09   ` Anthony G. Basile

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=288f8497-48d6-49c6-aa65-f7c480dc2aba@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=gentoo-musl@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox