git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	Julius Naperkowski <j.nap@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] Provide pessimistic defaults for cross compilation tests.
Date: Mon, 19 Jan 2009 18:49:03 -0800	[thread overview]
Message-ID: <7vab9mpu8w.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0901200037510.3586@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Tue, 20 Jan 2009 00:39:44 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> How do you deal with the hardcoded limitation that uname_S is defined to 
> be the output of "uname -s" on the _build_ system, and that quite a large 
> part of the Makefile sets variables dependent on this?
>
> IOW are you certain that configure (with your patch) will override _all_ 
> uname_S dependent settings?

It may be a valid question but it is not limited to cross compilation, is
it?  The matter is if values the Makefile wants to default to can be
overriden by whatever is placed in config.mak, and as long as that is Ok
we won't have a problem with or without use of configure (which is a
second class citizen).

  reply	other threads:[~2009-01-20  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 13:22 autoconf: C99 format check Julius Naperkowski
2009-01-16  9:41 ` Ralf Wildenhues
2009-01-19 20:34   ` [PATCH] Provide pessimistic defaults for cross compilation tests Ralf Wildenhues
2009-01-19 23:39     ` Johannes Schindelin
2009-01-20  2:49       ` Junio C Hamano [this message]
2009-01-20  6:59         ` Ralf Wildenhues
2009-01-20  6:50     ` Junio C Hamano
2009-01-20  7:04       ` Ralf Wildenhues

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=7vab9mpu8w.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j.nap@gmx.de \
    /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).