Am Sonntag, 25. Mai 2008 schrieb Nelson Ferreira:
> On Saturday 24 May 2008 07:54:19 pm Steve Youngs wrote:
> > * Nelson Ferreira <nelson.ferreira@xxxxxxxx> writes:
> > > On Friday 23 May 2008 11:28:31 pm Steve Youngs wrote:
> > >> * njsf <njsf@xxxxxxxxxxx> writes:
> > >> > /home/njsf/sandboxes/sxe/sxe-main/src/effi.c:1171: parse error
> > >> > before "cif"
> > >>
> > >> Here's the problem for this build failure (and all the other
identical
> > >> failures)...
> > >>
> > >> /usr/X11/include/ffi.h:63:23: ffitarget.h: No such file or directory
> > >>
> > >> For some reason it's not finding your ffitarget.h... symlink it into
> > >> that directory.
> > >
> > > Actually _no_, the problem is that /usr/X11/include is getting snuck
> > > into the compilation of effi and it _should not_.
> > >
> > > Now I do agree that Slack's idea of symlinking /usr/X11/include
> > > to /usr/include is bordering on the stupid, BUT, 3.1.1 is the only
> > > compiler that has problems with it....
> >
> > OK, so this is a compiler problem. Question is: do we want to try to
> > work around it, or do we just increase the minimum GCC version
> > requirement?
> >
> > I'm happy with either.
>
>
> I think we should try to work around it.
>
>
Hi,
with
sxemacs-22.1.9p141
from ./configure I get the following messages:
...
configure: WARNING: GCC FFI not found.
checking for ffi_call in -lffi... no
configure: WARNING: Cannot find a usable libffi, not compiling FFI support
checking for sufficient FFI support support... no
...
;;;;;;;;;
with
gcc (GCC) 4.2.1 (SUSE Linux)
Thanks a lot BTW
Andreas Röhler
|