Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] [MACOSX] problem with examples

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] [MACOSX] problem with examples


Chronologique Discussions 
  • From: tog <guillaume.alleon@gmail.com>
  • To: Nathalie Furmento <nathalie.furmento@labri.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] [MACOSX] problem with examples
  • Date: Wed, 6 Apr 2011 17:36:31 +0530
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Rv+kR6ifSeFwd+B5YNDZ22AAWM8xXa170wAYrWLNbSHwCgvO7wGDDydsU9jPcfsPNt Y5k01K7evr7cFyK6JgPU1AijGtN1ecpvoCuWS+vS2oCG/NQyRUnQNVE/6vo8s0krjPrk Kre2m3obZjp4YfvEDC33nTDNzRqdMp7VLa8nQ=
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

Hi,

Few things that might be different on my machine. It is running 64
bits i.e. in the menu About This Mac -> More info ... -> Software, I
have
64-bit Kernel and Extensions: Yes

obelix:starpu alleon$ uname -a
Darwin oggy.lan 10.7.0 Darwin Kernel Version 10.7.0: Sat Jan 29
15:16:10 PST 2011; root:xnu-1504.9.37~1/RELEASE_X86_64 x86_64


Then the answers to your questions:

obelix:starpu alleon$ ls -lrt mpi/tests/ring_kernel.cu
-rw-r--r-- 1 alleon staff 1125 Mar 29 14:14 mpi/tests/ring_kernel.cu


The output is attached.

Do you know how to enable OpenCL on the Mac ?

Best Regards
Guillaume

On Wed, Apr 6, 2011 at 5:09 PM, Nathalie Furmento
<nathalie.furmento@labri.fr> wrote:
> Hi,
>
> I tested on a MacOS with mpi and cuda, it is all working for me.
>
> Could you please check the file mpi/tests/ring_kernel.cu is available. And
> could you also please send the output of "make V=1".
>
> Thanks,
>
> Nathalie
>
> On 05/04/2011 13:51, tog wrote:
>>
>> Hi,
>>
>> Yes similar problems are there.
>> For examples, the mismatch between i386 and x86_64 can be solved by
>> adding the -m64 flag to nvcc (looks like mpicc generates 64 bits
>> objects, white the default for nvcc is 32 bits).
>> It might also be solved by adding -m32 to mpicc (not tested) - however
>> my machine is running 64 bits.
>>
>> Best Regards
>> Guillaume
>>
>> On Tue, Apr 5, 2011 at 4:30 PM, Nathalie Furmento
>> <nathalie.furmento@labri.fr>  wrote:
>>
>>>
>>> Hi,
>>>
>>> ring_kernel.o is build from ring_kernel.cu. The rule to build a .o from a
>>> .cu is in Makefile.am.
>>>
>>> Could you see if you also have the problems when building the tests or
>>> the
>>> examples (make -C tests or make -C examples)
>>>
>>> Thanks,
>>>
>>> Nathalie
>>>
>>>
>>> On 05/04/2011 12:35, tog wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> I still have a problem with the build in the mpi tests.
>>>>
>>>> if /usr/bin/mpicc -DHAVE_CONFIG_H -I. -I. -I../src/common -I../include
>>>> -I../gcc-plugin/src  -I../include/ -I../mpi/ -I../src/  -I../examples/
>>>> -I../src -I../include -D_GNU_SOURCE    -Wall -I/usr/local/cuda/include
>>>>  -O3  -gdwarf-2 -g3  -MT ring.o -MD -MP -MF ".deps/ring.Tpo" -c -o
>>>> ring.o `test -f 'tests/ring.c' || echo './'`tests/ring.c; \
>>>>        then mv -f ".deps/ring.Tpo" ".deps/ring.Po"; else rm -f
>>>> ".deps/ring.Tpo"; exit 1; fi
>>>> make[2]: *** No rule to make target `ring_kernel.o', needed by
>>>> `tests/ring'.  Stop.
>>>> make[1]: *** [all] Error 2
>>>> make: *** [all-recursive] Error 1
>>>>
>>>>
>>>> Any idea of what is wrong ?
>>>>
>>>> Best Regards
>>>> Guillaume
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>



--
PGP KeyID: 2048R/EA31CFC9  subkeys.pgp.net

Attachment: make.log
Description: Binary data




Archives gérées par MHonArc 2.6.19+.

Haut de le page