Re: Dicom package on Mac OS X

[Sebastian Schöps]

I am out of ideas. The problem of missing symbols (e.g. 
"_CFBundleCopyExecutableURL") is probably because of overwriting the 
DYLD_LIBRARY_PATH but might be also due to mixing compilers. However, I was not 
able to compile gdcm with the gcc in /usr/local/octave/3.8.0/bin. Maybe Carlo 
has some ideas.

If you really need the package, I propose to compile Octave using brew 
(http://www.brew.sh). This compiles here (using the patched version) without 
problems and this has the advantage that you do not have multiple compilers on 
you machine.

Am 04.06.2014 um 13:16 schrieb Miloslav Polasek <address@hidden>:
> 
> Ok, would you be so kind and provide a fool-proof list of commands that I 
> need to run to test this?
> Thanks,
> M.
> 
> On Jun 4, 2014, at 12:35 PM, c. <address@hidden> wrote:
> 
>> Hi,
>> 
>> Please remember to cc the list when answering.
>> 
>> On 4 Jun 2014, at 12:26, Miloslav Polasek <address@hidden> wrote:
>> 
>>> Hi,
>>> 
>>> thanks.
>>> 
>>> Yes, I installed Octave from the dmg file. What would you suggest? Should I 
>>> try to uninstall Octave and try to compile it from the source code? How 
>>> long can the whole process take? 
>>> Or is it possible just to disable gcc?
>> 
>> actually I suggest you do the opposite, i.e. try to compile
>> all libraries you need to link to using gcc rather than clang.
>> 
>> this essentially means adding /usr/local/octave/3.8.0/bin to your path
>> and defining a few environment variables so that libraries and headers
>> in /usr/local/octave/3.8.0/ are used first.
>> 
>> The reason why I am using gcc is that Octave needs a fortran compiler
>> to be built, and I never managed to make clang work well with libraries
>> built with gfortran (although this is theoretically meant to be possible).
>> 
>>> 
>>> M.
>> c.
>> 
> 
> 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/help-octave