From: Julius Schmidt <aiju@phicode.de>
To: 9front@9front.org
Subject: Re: [9front] bug: ape make eats lines after line continuations
Date: Wed, 12 Sep 2018 19:08:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1809121906260.15422@phi> (raw)
In-Reply-To: <4114921.6sTPCyEKaN@hugin>
No. No gmake in 9front.
We shouldn't add new non-native code without very good reason.
How does LLP64 break mksh? Is it casting pointers to long? (yuck)
On Wed, 12 Sep 2018, Jens Staal wrote:
> On Wednesday, 12 September 2018 18.26.14 CEST you wrote:
>> 9front's make in ape is eating newlines after line continuations
>> incorrectly. the attached makefile will produce the following output,
>> where 'fuck YOU' is the correct output.
>>
>> make on linux:
>>
>> $ make -s
>> objs one.o two.o
>> fuck YOU
>>
>> make on ape/psh:
>>
>> $ make -s
>> objs one.o two.o FUCK=YOU
>> fuck
>
> I am not sure how people would feel about it, but gmake is in fact building
> quite nicely under APE. There is an old port in the 9front ports and it should
> be easy to update.
>
> The same thing with gawk and gsed if anyone would be interested to use those
> for APE.
>
> The thing about the psh issue mentioned before: mksh builds nicely on i386
> (also available in ports). A problem with 64-bit is that Plan9 is LLP64, which
> messes up mksh building. Perhaps someone smarter than me could solve that.
>
>
>
next prev parent reply other threads:[~2018-09-12 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 16:26 Nick Owens
2018-09-12 16:34 ` [9front] " Jens Staal
2018-09-12 17:08 ` Julius Schmidt [this message]
2018-09-13 14:47 ` Nick Owens
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=alpine.LNX.2.00.1809121906260.15422@phi \
--to=aiju@phicode.de \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).