On Sep 6, 12:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Dear Arnaud,

Hi,

> This is really a sage building issue so should be taken to
> sage-support or sage-devel.
>
> As it happens I think that the change you suggest is already part of
> one of the patches athttp://trac.sagemath.org/sage_trac/ticket/3358
> (the *ungnu* one), so if you want to get this change incorporated, the
> best thing to do would be to review all that patch.

I am not a fan of the patch since it removes the possibility to build
eclib without certain options. We require gnu make for freetype
anyway, so building Sage without it is not possible.

Changing the occurances from make to ${MAKE}  is something I would
support, but in the end the benefit from it will be negligible.

> John Cremona

Cheers,

Michael

> CC: sage-devel
>
> 2008/9/6 Arnaud Bergeron <[EMAIL PROTECTED]>:
>
> > I am trying to make Sage compile on OpenBSD and I encountered some
> > problems with the eclib package related to the makefiles.
>
> > 'make' is hardcoded in all the makefiles and this package needs the
> > gnu version of make to build.  This makes it difficult to build on
> > systems that don't come standard with it since you have to override
> > your path to include a renamed copy of gmake in it before the standard
> > make.
>
> > The usual solution to this is to use ${MAKE} everywhere you call make
> > and this variable gets automagically set to the appropriate name to
> > call the make chosen by the user.  Attached is a patch against the
> > Sage package sources to do just this.  If you could include this in
> > the distribution it would make the life of BSD and possibly other unix
> > users easier.
>
> > Arnaud
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to