#29128 closed defect (duplicate)

pass the installation prefix of libffi to ECL

Reported by: dimpase Owned by:
Priority: critical Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: mkoeppe, isuruf, embray, fbissey, charpent, mmezzarobba Merged in:
Authors: Reviewers: Travis Scrimshaw
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by charpent)

at present ECL installation takes the headers of libffi from whereever it can, and first of all from "standard" locations. Thus an imcompatible libffi headers (and version 3.3 introduced an apparent incompatibility) installed system-wide break building of ECL even though --without-system-ecl is given.

This was reported to happen on Debian testing. (And an earlier related ticket is #21811). The initial debugging started on this thread of sage-devel.

ECL's configure has an option --with-libffi-prefix=path which hopefully does the job (untested); if so, this would at least allow the build to succeed in such a configuration.

Another task is to test for the incompatible libffi (well, we can just test the version not to be above 3.2.x for some x).

Change History (7)

comment:1 Changed 15 months ago by dimpase

  • Description modified (diff)

comment:2 Changed 15 months ago by charpent

  • Cc charpent added
  • Description modified (diff)

comment:3 Changed 15 months ago by mmezzarobba

  • Cc mmezzarobba added

comment:4 Changed 15 months ago by dimpase

In upstream ECL it's addressed in https://gitlab.com/embeddable-common-lisp/ecl/issues/302

So we hopefully can backport this to out 16.1.2, and support all versions of libffi, old and current.

comment:5 Changed 15 months ago by dimpase

  • Milestone changed from sage-9.1 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

the ECL's option appears not be working, anyway, on #21811 there is a better solution. We'll fix the issue on #21811

comment:6 Changed 14 months ago by tscrim

  • Reviewers set to Travis Scrimshaw
  • Status changed from needs_review to positive_review

Since #21811 is a better solution and positively reviewed, I agree with closing this.

comment:7 Changed 14 months ago by chapoton

  • Resolution set to duplicate
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.