You can avoid the openlibm issue for now by adding

override USE_SYSTEM_LIBM=1

in your Make.user. Can you also file this issue in the openlibm github 
repo, so that it can be fixed. Should be easy.

I wonder why your build is picking up llvm 3.5.0, since ARM.inc uses 3.5.1 
now. I don't know if that will fix the build problem. Make sure that your 
new gcc is the default (with gcc -v), and if still trouble, add 
--disable-compiler-version-checks to LLVM_FLAGS in the ARM.inc.

-viral

On Monday, February 16, 2015 at 4:12:06 PM UTC+5:30, Sto Forest wrote:
>
> After adding in a couple of dependencies, gfortran, cmake, compilation is 
> getting further.
>
> There are two current problems:
>
> *openlibm*
>
> s_creall.c:(.text+0x0): multiple definition of `creal'
> src/s_creal.c.o:s_creal.c:(.text+0x0): first defined here
> collect2: error: ld returned 1 exit status
> Makefile:35: recipe for target 'libopenlibm.so' failed
> make[3]: *** [libopenlibm.so] Error 1
> Makefile:686: recipe for target 'openlibm/libopenlibm.so' failed
> make[2]: *** [openlibm/libopenlibm.so] Error 2
> make[2]: *** Waiting for unfinished jobs....
> ar: creating libcerbla.a
>
>
> *LLVM*
> I upgraded gcc to version *gcc (Raspbian 4.8.2-21~rpi3rpi1) 4.8.2.*
>
> However, when running *make *in /opt/julia it errors over the compiler 
> version not being new enough:
>
> checking whether GCC is new enough... no
> configure: error:
> The selected GCC C++ compiler is not new enough to build LLVM. Please 
> upgrade
> to GCC 4.7. You may pass --disable-compiler-version-checks to configure to
> bypass these sanity checks.
> Makefile:508: recipe for target 
> 'llvm-3.5.0/build_Release+Asserts/config.status' failed
> make[2]: *** [llvm-3.5.0/build_Release+Asserts/config.status] Error 1
> Making all in UTIL
>
>
> Any suggestions from more knowledgeable people would be welcomed :)
>
>
>
>
>
>
>
>
> On Sunday, 15 February 2015 19:04:02 UTC, Sto Forest wrote:
>>
>> Thanks Steve I'll give that a try and see how far I get. :)
>>
>>
>> On Sunday, 15 February 2015 01:06:39 UTC, Steve Kelly wrote:
>>>
>>> Sto, 
>>>
>>> I got Julia running on a BeagleBone Black running Debian Jessie a couple 
>>> months back using this process: 
>>> https://github.com/JuliaLang/julia/blob/master/README.arm.md. It 
>>> depends on a few system libraries to run, so I needed to update from Wheezy 
>>> to Jessie so it would work. I think some improvements have been made since 
>>> then so the build is more self contained. I am pretty sure Raspbian is 
>>> based on Wheezy, but it might be worth a shot with the latest master.
>>>
>>> Best,
>>> Steve
>>>
>>> On Sat, Feb 14, 2015 at 3:11 PM, Sto Forest <[email protected]> 
>>> wrote:
>>>
>>>> Is there a way to get Julia running on the new Raspberry Pi 2, perhaps 
>>>> under raspbian ? 
>>>>
>>>>
>>>>
>>>

Reply via email to