From: Ashish SHUKLA <ashish.is@lostca.se>
To: Andrea Corallo <akrl@sdf.org>
Cc: 40462@debbugs.gnu.org
Subject: bug#40462: 28.0.50; Building nativecomp branch segfaulting on FreeBSD
Date: Sat, 2 May 2020 14:21:59 +0530 [thread overview]
Message-ID: <a7554ce5-6e58-7bbe-9f71-55f53ea2dae9@lostca.se> (raw)
In-Reply-To: <36bcd418-21d6-5fa3-a1cf-9820870ca889@lostca.se>
[-- Attachment #1.1: Type: text/plain, Size: 744 bytes --]
On 5/2/20 1:52 PM, Ashish SHUKLA wrote:
> On 5/2/20 1:24 PM, Ashish SHUKLA wrote:
>
> [...]
>
>> I used the FreeBSD ports to install everything. Whereas you used GCC
>> from trunk unlike me, and used these GNU make arguments, which I wasn't.
>>
>>
>> Anyways, I'll report back with my results.
>
> It's still building, but at least it passed the previous stage where it
> was segfaulting after switching to the gmake command-line arguments:
>
> NATIVE_FAST_BOOT=1 V=1
>
> So, that seems like a good sign.
>
> I will report back, when it completes.
It completed few minutes ago, with no issues. So, it seems like I was
using the wrong command-line for building. Sorry about that.
Thanks!
--
Ashish SHUKLA
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-02 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 9:00 bug#40462: 28.0.50; Building nativecomp branch segfaulting on FreeBSD Ashish SHUKLA
2020-04-06 9:04 ` Ashish SHUKLA
2020-04-18 11:15 ` Andrea Corallo
2020-04-18 15:46 ` Ashish SHUKLA
2020-04-18 16:29 ` Andrea Corallo
2020-04-30 20:36 ` Ashish SHUKLA
2020-04-30 20:49 ` Andrea Corallo
2020-05-01 5:19 ` Ashish SHUKLA
2020-05-01 8:53 ` Andrea Corallo
2020-05-01 22:03 ` Andrea Corallo
2020-05-02 7:54 ` Ashish SHUKLA
2020-05-02 8:22 ` Ashish SHUKLA
2020-05-02 8:51 ` Ashish SHUKLA [this message]
2020-05-02 9:57 ` Andrea Corallo
2020-05-02 12:59 ` Ashish SHUKLA
2020-05-02 13:15 ` Andrea Corallo
2020-05-03 9:27 ` Andrea Corallo
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7554ce5-6e58-7bbe-9f71-55f53ea2dae9@lostca.se \
--to=ashish.is@lostca.se \
--cc=40462@debbugs.gnu.org \
--cc=akrl@sdf.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).