Hi Mikael,

I tried to build pocl using your script but it failed because it couldn't
find the clang header files. To solve this problem, I copied the clang
header files to "/C/pocl-playground/llvm/include". After that, I was
finally be able to build pocl.
However, I couldn't compile an OpenCL program using pocl. The LNK2019 error
occurs during the compilation (Please see the attachment).

And I agree that putting this script there would be useful.

Thank you,
Volkan

On Sat, Jan 24, 2015 at 1:32 PM, Mikael Lepistö <[email protected]>
wrote:

> Hi, Volkan
>
> I found out what caused linking problems. Looks like there was no
> -DSTATIC_LLVM=ON passed successfully to cmake, and CMakeFile is using path:
>
>   else()
>     set(POCL_LLVM_LIBS "${LLVM_LIBS}")
>     message(STATUS "LLVM-${LLVM_VERSION} library not found (Probably
> because LLVM is built with cmake).
>     Linking libpocl (possibly statically) to LLVM_LIBS")
>   endif()
>
> to set POCL_LLVM_LIBS. ${LLVM_LIBS} here contains list:
> "-lLLVMxxx;-lLLVMyyy;-lLLVMzzz" which does not work with Visual Studio. We
> could add check in there, if (MSCV) and show error in this case, or
> actually set(POCL_LLVM_LIBS "${LLVM_LIB_NAMES}") for all platforms, which
> should work platform compatible.
>
> So in short I was just able to compile latest pocl against llvm 3.5 with
> running script attached (I did set up Windows 8.1 trial to Virtual Box to
> test it out with clean Windows installation). One just needs to have Cmake,
> Python, Git Bash and Visual Studio 2013 (e.g. Community Edition) pre
> installed for script to run. Let me know how it works. I'm going to test
> compiling against llvm 3.6 next.
>
> README.Windows had some errors there (mostly vague / incomplete commands),
> maybe it would be more clear to just put this script there instead.
>
> Cheers, Mikael
>
>
> On Wed, Jan 7, 2015 at 10:02 AM, Mikael Lepistö <[email protected]>
> wrote:
>
>> Hi Volkan,
>>
>> I'm sorry for the delay. I haven't got time to look into this yet. I'm
>> currently looking if it would be possible to setup some scripts to install
>> all dependencies to make easily reproducible build system. Then one could
>> get Windows testing box e.g. with Vagrant (
>> http://blog.syntaxc4.net/post/2014/09/03/windows-boxes-for-vagrant-courtesy-of-modern-ie.aspx)
>> or by downloading directly from https://www.modern.ie/en-us and do
>> windows build / run tests there and make debugging windows problems easier.
>>
>> It would be nice to be able to share modern.ie virtual image, with
>> preinstalled software, but that probably breaks pretty much all user
>> agreements :) How ever you are allowed to make one backup of virtual
>> machine for your self, so it could be enough for buildbot usage.
>>
>> - Mikael
>>
>> On Tue, Dec 16, 2014 at 11:04 AM, Volkan Keleş <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> Using LLVM 3.5 (MinSizeRel), CMake configurates without replacing the
>>> value of `LLVM_HOST_TARGET` but building the solution still fails. See
>>> `LOG_MSVS_LLVM_35_MinSizeRel.txt` and `LOG_CMAKE_LLVM_35_MinSizeRel.txt`.
>>>
>>> Volkan
>>>
>>> On Fri, Dec 12, 2014 at 3:37 PM, Mikael Lepistö <
>>> [email protected]> wrote:
>>>>
>>>> I compared your cmake.log with mine and I found straight couple of
>>>> differences. You seem to use llvm 3.4. I haven't tested this with 3.4, but
>>>> only with 3.5 and I'm building llvm as MinSizeRel... but that probably is
>>>> not a problem. Could you try if llvm 3.5 works better?
>>>>
>>>> - Mikael
>>>>
>>>> On Fri, Dec 12, 2014 at 12:54 PM, Volkan Keleş <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Mikael,
>>>>>
>>>>> I added the CMake log of the successful running (See
>>>>> LOG_CMAKE_x86_64-pc-win32.txt).
>>>>>
>>>>> Volkan
>>>>>
>>>>> On Thu, Dec 11, 2014 at 5:09 PM, <
>>>>> [email protected]> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Looks like for some reason static llvm*.lib files are not linked in
>>>>>> correctly on your platform... maybe it needs some addition to cmake's
>>>>>> link_directories() to find libs.. do you have cmake log from
>>>>>> successful
>>>>>> running of cmake with x86_64-pc-win32 target.
>>>>>>
>>>>>> Btw. changing x86_64-px to x86_64-pc-win32 might fail later on when
>>>>>> compiling kernel library to .bc where at some point windows name
>>>>>> mangler
>>>>>> had not implemented enough stuff to be able to mangle some opencl
>>>>>> overridden function names.
>>>>>>
>>>>>> Good luck, Mikael
>>>>>>
>>>>>> On Thu, Dec 11, 2014 at 2:25 PM, Volkan Kele? <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>> > Hi,
>>>>>> >
>>>>>> > I have been trying to build pocl on Windows and I keep getting some
>>>>>> errors.
>>>>>> >
>>>>>> > Firstly, I tried to build as described in "README.Windows" but CMake
>>>>>> > failed (See LOG_CMAKE.txt [*]). Then I replaced the value of
>>>>>> > `LLVM_HOST_TARGET` (LLVM.cmake:114)  with "x86_64-pc-win32". Now,
>>>>>> the
>>>>>> > configuration completes but building the solution fails (See
>>>>>> LOG_MSVC.txt
>>>>>> > [*]). I guess some parts of the configuration properties are not
>>>>>> correct.
>>>>>> >
>>>>>> > Do you have any idea about these errors?
>>>>>> >
>>>>>> > [*]
>>>>>> >
>>>>>> https://www.dropbox.com/sh/grw0unevw7uxowm/AABB_fot6-mcllce0dSyctG2a?dl=0
>>>>>> >
>>>>>> > Volkan
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> ------------------------------------------------------------------------------
>>>>>> > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>>>> > from Actuate! Instantly Supercharge Your Business Reports and
>>>>>> Dashboards
>>>>>> > with Interactivity, Sharing, Native Excel Exports, App Integration
>>>>>> & more
>>>>>> > Get technology previously reserved for billion-dollar corporations,
>>>>>> FREE
>>>>>> >
>>>>>> >
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>>>>> > _______________________________________________
>>>>>> > pocl-devel mailing list
>>>>>> > [email protected]
>>>>>> > https://lists.sourceforge.net/lists/listinfo/pocl-devel
>>>>>> >
>>>>>> >
>>>>>> -------------- next part --------------
>>>>>> An HTML attachment was scrubbed...
>>>>>>
>>>>>> ------------------------------
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>>>> from Actuate! Instantly Supercharge Your Business Reports and
>>>>>> Dashboards
>>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration &
>>>>>> more
>>>>>> Get technology previously reserved for billion-dollar corporations,
>>>>>> FREE
>>>>>>
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>>>>>
>>>>>> ------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> pocl-devel mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>>> from Actuate! Instantly Supercharge Your Business Reports and
>>>>> Dashboards
>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration &
>>>>> more
>>>>> Get technology previously reserved for billion-dollar corporations,
>>>>> FREE
>>>>>
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> pocl-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>>> with Interactivity, Sharing, Native Excel Exports, App Integration &
>>>> more
>>>> Get technology previously reserved for billion-dollar corporations, FREE
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> pocl-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>> Get technology previously reserved for billion-dollar corporations, FREE
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> pocl-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> pocl-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>
>
1>------ Build started: Project: POCL_Test, Configuration: Debug Win32 ------
1>Source.obj : error LNK2019: unresolved external symbol _clGetPlatformIDs@12 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clGetDeviceIDs@24 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clCreateContext@24 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clReleaseContext@4 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clCreateCommandQueue@20 referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clReleaseCommandQueue@4 referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clCreateBuffer@24 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clReleaseMemObject@4 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clCreateProgramWithSource@20 referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clReleaseProgram@4 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clBuildProgram@24 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clCreateKernel@12 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clReleaseKernel@4 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clSetKernelArg@16 
referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clFlush@4 referenced 
in function _main
1>Source.obj : error LNK2019: unresolved external symbol _clFinish@4 referenced 
in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clEnqueueReadBuffer@36 referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clEnqueueWriteBuffer@36 referenced in function _main
1>Source.obj : error LNK2019: unresolved external symbol 
_clEnqueueNDRangeKernel@36 referenced in function _main
1>c:\users\vlknk_000\documents\visual studio 
2013\Projects\POCL_Test\Debug\POCL_Test.exe : fatal error LNK1120: 19 
unresolved externals
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to