On Mon, Oct 8, 2012 at 8:48 AM, Rupert Swarbrick <rswarbrick@...> wrote:
> Faré <fahree@...> writes:
>> On Mon, Oct 8, 2012 at 2:34 AM, Nikodemus Siivola
>>> commit d15afa61c4854eddb4b61e3d8772590db760c565
>>> Author: Nikodemus Siivola <nikodemus@...>
>>> Date: Mon Oct 8 08:49:41 2012 +0300
>>>
>>> allow SB-CONTRIB operation without explicitly set CC
>>>
>>> Fall back to "cc" with a style-warning.
>>>
>> Shouldn't it instead remember the compiler and options used while
>> compiling SBCL itself?
>
> At least on Linux machines, mostly people are going to be installing
> binary SBCL packages (eg. .debs, rpms, ...). The compiler installed on
> the build machine doesn't a priori have much connection with that
> installed locally.
>
> Maybe I've misunderstood your question?
>
Oh yes, there will be a strong connection.
In particular, -m32 vs -m64 flags are *essential*,
as well as any other flags that modify the ABI.
Failing to remember these is planning to fail.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Most economic fallacies derive... from the tendency to assume that there
is a fixed pie, that one party can gain only at the expense of another.
— Milton Friedman
|