unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: Problem with removing <config.h> from gen-scmconfig when cross-compiling
Date: Sun, 16 Mar 2014 23:48:31 -0700	[thread overview]
Message-ID: <CAP9bCMTUU6nJXaHTNERhT3268__K-1AnSuC4M1BnKCP93P6+Rw@mail.gmail.com> (raw)
In-Reply-To: <87lhwenfdt.fsf@gnu.org>

On Thu, Mar 13, 2014 at 11:05 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Dale Evans pointed out that GCC runs the autoconf tests twice when
>> cross-compiling: once for the build machine and once for the host
>> machine.  I suspect that this is the proper solution for us, so we'd
>> end up with two config.h files.
>
> Yes, but GCC's configure machinery is really the next level...

What does "the next level" mean?



  parent reply	other threads:[~2014-03-17  6:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  1:23 Problem with removing <config.h> from gen-scmconfig when cross-compiling Mark H Weaver
2014-03-13 13:37 ` Ludovic Courtès
2014-03-13 15:16   ` Mark H Weaver
2014-03-13 15:47     ` Ludovic Courtès
2014-03-13 16:37       ` Mark H Weaver
2014-03-13 18:05         ` Ludovic Courtès
2014-03-14 21:43           ` Mark H Weaver
2014-03-17  6:48           ` Doug Evans [this message]
2014-03-17 20:32             ` Ludovic Courtès
2014-03-18  1:45               ` Doug Evans
2014-03-13 17:00       ` Mark H Weaver
2014-03-13 18:23         ` Ludovic Courtès

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP9bCMTUU6nJXaHTNERhT3268__K-1AnSuC4M1BnKCP93P6+Rw@mail.gmail.com \
    --to=xdje42@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).