unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 48116-done@debbugs.gnu.org, Anatole Dahan <dahan@imj-prg.fr>
Subject: bug#48116: Problems when cross-compiling native-comp
Date: Wed, 07 Jun 2023 17:38:45 -0400	[thread overview]
Message-ID: <yp18rcv9cm2.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <xjfy2cwvmh6.fsf@sdf.org> (Andrea Corallo's message of "Sun, 02 May 2021 21:45:25 +0000")

Andrea Corallo <akrl@sdf.org> writes:

> Anatole Dahan <dahan@imj-prg.fr> writes:
>
>> Hi,
>>
>> I have encountered errors while configuring emacs, and I was told to send a bug report here. You will find my config.log attached, together with my environment variables.
>>
>> For context, I am trying to cross-compile native-compilation. I guess
>> this might not be supported, as libgccjit makes it quite complicated
>> (I didn’t yet find a way to bypass the smoke test). I have built the
>> NATIVE libgccjit for i586-linux-musl (maybe I am wrong about that ?)
>>
>> Anyway, both sys/inotify.h and libgccjit.h are present, but they are
>> marked as missing because they can’t be used (which seems legit, at
>> least for libgccjit, since it is built for native
>> i586-linux-musl). From what I understood, this is considered a bug.
>>
>> Best,
>> —Anatole Dahan
>
> Hi Anatole,
>
> generally speaking we do not support cross compilation using the native
> build as libgccjit AFAIK is just not made for cross compiling.  I
> suspect in your specific case this should be possible with some hacking
> but coming to the problem of bypassing the smoke test I think the
> easiest is to start with is commenting it out from configure.ac.

Closing this old bug as, as mentioned, we (and libgccjit as well) don't
support cross native compiled builds.

Best Regards

  Andrea






      reply	other threads:[~2023-06-07 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 10:30 bug#48116: Headers presents but unusable Anatole Dahan
2021-05-02  7:31 ` Lars Ingebrigtsen
2021-05-02 21:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-07 21:38   ` Andrea Corallo [this message]

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=yp18rcv9cm2.fsf_-_@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=48116-done@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=dahan@imj-prg.fr \
    /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).