Re: [eclipse-users] Max OS X install

Dear Kish,

I get the following compile error:

LD_LIBRARY_PATH=/vol/Eclipse/thirdparty/coin/x86_macosx/lib: 
../bin/x86_macosx/eclipse -e 
'get_flag(library_path,P),set_flag(library_path,["."|P]),lib(fcompile), 
set_flag(variable_names,off), fcompile("graph_algorithms", 
[outdir:"../lib"])'
dyld: Library not loaded: libeclipse.dylib
  Referenced from: /Users/brammert/Eclipse/lib/x86_macosx/eclipse.exe
  Reason: image not found
make[1]: *** [../lib/graph_algorithms.eco] Trace/BPT trap
make: *** [make_icparc_solvers] Error 2

ciao,

Brammert

Kish Shen schreef:
> On Thursday 22 March 2007 05:24, you wrote:
>
>   
>> Step 4) When trying to build libeclipse.dylib there is a libtool error:
>>
>> libtool: can't locate file for: -lgcc
>> libtool: file: -lgcc is not an object file (not allowed in a library)
>>
>> Removed the -lgcc from line 1653 of configure:
>>
>>      DYNLDFLAGS="-dynamic -single_module -flat_namespace -lgcc"
>>
>>     
>
> I think the -lgcc was needed in the 10.2 PPC OSX build [which was what we were able to
> build on], to load the  (gcc) C library. [See my reply to Brammert later]
>
>   
>> Step 5) Now libtool gives a different error:
>>
>> /usr/local/lib/libgmp.a(add_n.o) has local relocation entries in non- 
>> writable section
>>
>> This one has me stuck. Poking around the web seems to indicate that  
>> others have had this problem with libgmp on the Mac, but I cannot  
>> find any answers yet. It may be a fundamental problem with GMP.
>>
>> Malcolm
>>
>>     
>
> As Joachim said, you can build without gmp support. This means that the ECLiPSe build will
> only have normal integer (i.e. 32 bits for 32 bits machines) support. 
>
> However, I have been able to get ECLiPSe to link with libgmp for the PPC Mac OSX (10.2), so
> unless the problem is somehow specific to the Intel Macs, it should be able to link against this.
> I think this libgmp.a is not something you installed for building ECLiPSe? Is it really 
> trying to link with a .a rather than a .dylib file? Could this be the problem?
>
> I am pretty sure that we linked against a libgmp.dylib (version 4.1) that was built in the 
> ECLIPSETHIRDPARTY directory when I built the binaries for the PPC Mac OSX on 
> SourceForge's compile farm machine. Unfortunately they have withdrawn that service and
> I cannot check this anymore. 
>  
> There is a more detailed description (than in the INSTALL file provided with the source) of
> building ECLiPSe from the source in:
>
> http://eclipse.crosscoreop.com/reports/SetupGuideV2.pdf
>
> This doesn't specifically address the Intel Mac issues, but may be helpful for other things.
>
>
> On Thursday 22 March 2007 10:57, brammert wrote:
>   
>> I have also been trying to compile eclipse on an intel mac and have run into the same problem. 
>> The thing is that libtool does not know where gcclib.a is located. If you use g++ as the DYLD 
>> instead of libtool it does work, because g++ adds the path to the final link call.  
>>     
>
> I assume this is for the -lgcc problem. I think it may be better to use gcc instead of g++ as we
> are compiling C rather than C++ here. I think I used libtool because gcc did not do the linking
> properly on the OS X 10.2 we were using.
>
>   
>> However, after that I hit another problem that I myself have not been able to solve so far.
>> At some point one reaches the make_icparc_solver. In it's makefile at some point the eclipse 
>> binary is called. However, it is not able to find libeclipse.dylib. I have not been able to find 
>> the problem on that one yet.   
>>     
>
> libeclipse.dylib should be in <ECLiPSe>/lib/<ARCH>libeclipse.dylib
>
> where ARCH is ppc_macosx for the PPC build (or the fake PPC build).
>
> Can you send us the exact messages you are getting? ECLiPSe used to print a misleading 
> error message about not finding the dynamic library whenever there is a problem loading 
> the library, not just when it is unable to find the library.
>
> Thanks and cheers,
>
> Kish
>
>
>