#20136: Various meataxe build issues
-------------------------------------------------+-------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-7.1
Component: packages: optional | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: Reported upstream. Developers | Work issues:
acknowledge bug. | Commit:
Branch: | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Comment (by SimonKing):
Replying to [comment:37 jdemeyer]:
> No! I am suggesting to split up your patches in two directories: one to
be applied at install-time as usual and one to apply at packaging-time.
Please have a closer look at the `build/pkgs/ecl/patches/` directory.
Exactly. All patches in `build/pkgs/ecl/patches/` (`gmp.patch`,
`implib.patch`, `write_error.patch`) are applied by `spkg-src`, which
contains the lines
{{{
# the patches are applied here, as it has to be done before
# running autoconf.
cd src
echo "applying patches in ecl-$ECLVERSION/src"
# For some of the patches, Cygwin also has upstream fixes that are
# closely related, keep track. See Trac 11119, for example.
for patch in ../../patches/*.patch; do
patch --verbose -p2 <"$patch"
if [ $? -ne 0 ]; then
echo >&2 "Error applying '$patch'"
exit 1
fi
done
}}}
That's why I was asking.
Unless there was a change since sage-7.1.
--
Ticket URL: <http://trac.sagemath.org/ticket/20136#comment:38>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
