This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libffi - the 10th Anniversary Release


Eli Barzilay wrote:
This is possibly a stupid question -- but aren't the main sources in
the gcc subversion repository?
It's a good question. What we have here is a case of the tail wagging the dog...

The libffi tree in gcc is definitely the most up to date and well maintained tree, however the GCC project views libffi as an external project that they include for convenience sake. It seems perfectly reasonable to populate the stand-alone libffi tree from the GCC project to make a release for users. This simply mirrors what some projects using libffi do on their own anyways.

In any case, I'd appreciate it if people would like to try checking
out the latest from the libffi cvs repository and build/test it.

FWIW, we (www.plt-scheme.org) recently updated our copy from the gcc repository, and it builds fine -- we have these patches:

* We recreated libffi/configure with autoconf version 2.61

 * We changed config/multi.m4 (not inthe libffi directory) to allow
   in-source-tree builds, the change is from line:

if test "$with_target_subdir" != "."; then

to

if test ! -z "$with_target_subdir" && test "$with_target_subdir" != "."; then

 * Removed +live_support in src/powerpc/darwin_closure.S so it builds
   with Mac OS X 10.
Thanks for the input. Why do you have to remove the live_support section attribute? Is it just because Max OS X 10 tools don't recognize it? Is this something we should have a configure test for?

Thanks again,

AG


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]