#13325: eclib does not build on Cygwin
------------------------------------------------------------+---------------
Reporter: jpflori | Owner:
tbd
Type: defect | Status:
needs_review
Priority: major | Milestone:
sage-5.3
Component: cygwin | Resolution:
Keywords: eclib spkg cygwin | Work issues:
Report Upstream: Workaround found; Bug reported upstream. | Reviewers:
Authors: Jean-Pierre Flori | Merged in:
Dependencies: #13333 | Stopgaps:
------------------------------------------------------------+---------------
Comment (by jpflori):
Replying to [comment:28 jpflori]:
> Replying to [comment:27 cremona]:
> > 1. will no longer be necessary. These flags are now set i nthe
various Makefile.am using the macros LIBADD and LDADD, and I did put gmp
last.
> Great.
> >
> > 2. $(EXEEXT). I assume that this is set on cygwin (to ".exe" or
something) but not otherwise, so (apart from cluttering up the Makefiles)
there will be no effect on other systems? You say that this is done in
src/tests, but should it also be done in src/progs? The latter builds
some binaries which are actually installed (e.g. mwrank).
> Yes, this is only "really" needed on Cygwin.
> On most systems, let's say Linuxes, $(EXEEXT) will be void, so putting
it or not won't have any visible effect.
>
> If I remember correctly, the executables in the progs directory already
magically included the $(EXEEXT) (or at least the file produced ended up
in .exe).
> There must be some difference between the two Makefile.am you used.
> I can have a look if you want.
Disregard this last comment, I did not get what you said.
The splitting of progs and tests is posterior to the current spkg Sage
ships.
But yes, I guess you could add $(EXEEXT) everywhere I guess, I must admit
I don't really really remember if this is really necessary on Cygwin...
but on Windows executables usually finish with .exe, so it can not hurt.
Plus, on recent Cygwin versions, there seems to be some automatic
translation from prog to prog.exe (I guess this also made my changes
actually work when setting SAGE_CHECK, because I did not add $(EXEEXT) at
each invocation of the programs as I just realized).
> >
> > 3. '-no-indefined' OK I can add that too. By the way, the library
name is now libec and not libjc.
> Great (jsut beware of the typo here :)
> >
> > 4. OK, so I'm a bit uncertain as to which auto* files to actually
include. When I change configure.ac or any Makefile.am files I run
autoreconf. I never touch or look at configure or the actual Makefiles.
> I'm not really sure of what should be included in a distribution
tarball, I've begun fighting with autotools just a few weeks ago.
> What was really painfull here is that it seemed that having a more
recent configure than aclocal.m4 was detected by configure itself and let
it try to regenerate aclocal.m4 (which failed because of the lack of a
proper m4 directory with I don't really know what macros inside).
> The same was true for Makefile.in.
>
> Don't know what the behavior if you actually omit the configure.ac and
Makefile.am files.
> >
> > So I will now deal with points 2 and 3 and hand back to you, if that
is OK.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13325#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
