On 29 Okt., 06:37, Peter Jeremy wrote:
> On 2010-Oct-28 02:31:19 -0700, Volker Braun wrote:
>
> >Making every 3rd party author adhere to the standard usage of CC/CXX
> >is a bit like herding cats. It would be the cleanest fix to patch all
> >the different build systems, sure. But wouldn't it be e
On 2010-Oct-28 02:31:19 -0700, Volker Braun wrote:
>Making every 3rd party author adhere to the standard usage of CC/CXX
>is a bit like herding cats. It would be the cleanest fix to patch all
>the different build systems, sure. But wouldn't it be easier if Sage
>would set up its own gcc wrapper in
On 10/28/10 02:34 PM, Alexandre Blondin Massé wrote:
In that case, since it's compiling a C++ file, the variable should be called
CXX, so changing to
$(CXX) $(CFLAGS) -c cubex.cpp
and removing the line
CC=g++
makes it use Sage's variable.
It doesn't change much to the problem, but instead o
On 28 Oct, 08:17, "Dr. David Kirkby" wrote:
> On 10/28/10 06:37 AM, Minh Nguyen wrote:
>
>
>
>
>
>
>
>
>
> > Hi David,
>
> > On Thu, Oct 28, 2010 at 2:51 PM, Dr. David Kirkby
> > wrote:
> >> The fact Sage does not reliably respect the CC and CXX variables is a pain
> >> if you want to use a no
>
> In that case, since it's compiling a C++ file, the variable should be called
> CXX, so changing to
>
> $(CXX) $(CFLAGS) -c cubex.cpp
> and removing the line
> CC=g++
>
> makes it use Sage's variable.
>
It doesn't change much to the problem, but instead of removing the
line
CC = g++
I think you
On 2010-10-28 11:31, Volker Braun wrote:
> Making every 3rd party author adhere to the standard usage of CC/CXX
> is a bit like herding cats. It would be the cleanest fix to patch all
> the different build systems, sure. But wouldn't it be easier if Sage
> would set up its own gcc wrapper in $SAGE_
Making every 3rd party author adhere to the standard usage of CC/CXX
is a bit like herding cats. It would be the cleanest fix to patch all
the different build systems, sure. But wouldn't it be easier if Sage
would set up its own gcc wrapper in $SAGE_LOCAL/bin? The first step of
the Sage build proce