Thanks Kish. I'm really only concerned with getting it to compile currently, not the 3rd party features - I'll try to deal with those later. The 6.0#183 binary on SourceForge does work on OS X 10.8. Here's the compiling output that includes references to libeclipse.dylib: ---------------------------------------- gcc -dynamiclib -single_module -flat_namespace -search_paths_first -m64 -mmacosx-version-min=10.4 -L -o libeclipse.dylib \ dict.o read.o lex.o emu.o proc_desc.o bip_tconv.o io.o write.o bip_comp.o mem.o operator.o bip_record.o bip_bag.o bip_heapevents.o bip_shelf.o bip_store.o bip_array.o bip_strings.o bip_db.o property.o bip_io.o procedure.o handle.o intervals.o bip_arith.o bigrat.o bip_module.o bip_control.o bip_delay.o bip_domain.o bip_misc.o elipsys_fd.o bip_load.o code.o init.o emu_c_env.o emu_util.o error.o external.o gc_stacks.o handlers.o printam.o addrmap.o eclipsedir.o embed.o os_support.o lib1.o lib2.o lib3.o lib4.o lib5.o lib6.o lib7.o dummy_mps.o dummy_par.o dummy_upcalls.o dummy_wm.o whereami_default.o \ -L../../lib/x86_64_macosx -L../..//sys_lib/x86_64_macosx \ -lshm -L. -lgmp -ldl -lm i686-apple-darwin11-llvm-gcc-4.2: libeclipse.dylib: No such file or directory ---------------------------------------- Like Paulo I have a libeclipse.a in the Kernel/x86_64_macosx directory. Looks like the problem is the "-L" before the "-o libeclipse.dylib". If anyway can put together how the SourceForge binaries were compiled that would be nice. On Sun, Oct 7, 2012 at 1:00 AM, Kish Shen <kisshen_at_...5...> wrote: > Hi Dave, > > The ECLiPSe Mac OS X x86 binaries from SourceForge are built on Mac OS > 10.6. > > The single error message you have given is not enough to show what might > be going wrong. In particular, I am not sure if the problem is caused by > compiling on 10.8. I can't really tell where exactly the error message is > from, and what exactly configure did. Is there a libeclipse.dylib (it > should be in Kernel/x86_64_macosx directory)? If not, there should have > been some earlier error when the building of libeclipse.dylib failed. > > You don't seem to have set ECLiPSETHIRDPARTY environment variable for > your build, and this probably means that few third-party components will > be used for your build (configure should report what it was able to find). > For ECLiPSe 6.0 onwards, we strongly recommend that you build ECLiPSe with > at least bignum support, i.e. with GNU GMP (or GMP compatible lib -- for > x86 Macs I use MPIR instead of GMP), because without bignums, the new > ECLiPSe compiler can only compile clauses with limited number of variables, > and some of ECLiPSe's own files cannot be compiled). However, I don't think > this is the direct cause of your error, as your error seem to be happening > earlier than this. > > Cheers, > > Kish > > > > On 06/10/2012 12:48, David Dreisigmeyer wrote: > >> Has anyone has compiled ECLiPSe on OS X 10.8? If so would you be able to >> provide any details on how to go about doing it, especially for 6.0#196? >> The binary for 6.0#183 from SourceForge works though I can't get it to >> compile, ending with the error: >> >> i686-apple-darwin11-llvm-gcc-**4.2: libeclipse.dylib: No such file or >> directory >> >> I'm attempting to compile as follows: >> >> $ export ARCH=x86_64_macosx >> $ ./configure >> $ make -f Makefile.$ARCH >> >> Thanks, >> >> -Dave >> >> >> >> This body part will be downloaded on demand. >> >> >> >> This body part will be downloaded on demand. >> >> > -- *Go Blue!*Received on Mon Oct 08 2012 - 00:30:09 CEST
This archive was generated by hypermail 2.3.0 : Tue Apr 16 2024 - 09:13:20 CEST