cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
richard12345
Visitor
Visitor
2,345 Views
Registered: ‎01-19-2018

HLS build fail in Windows 10

Hi , 

 

This is Richard from SystemView inc.

When i build HLS in windows 10, it comes 

C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\exception_ptr.h:132:13: error: unknown type name 'type_info'
      const type_info*
C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\nested_exception.h:62:5: error: the parameter for this explicitly-defaulted copy constructor is const, but a member or base requires it to be non-const
    nested_exception(const nested_exception&) = default;

the same code has no problem in Linux environment.

 

0 Kudos
7 Replies
hbucher
Scholar
Scholar
2,322 Views
Registered: ‎03-22-2016

@richard12345 Can you post the actual code you are trying to compile? Perhaps just the offending part...

What version of HLS you're running on Windows? And on Linux?

vitorian.com --- We do this for fun. Always give kudos. Accept as solution if your question was answered.
I will not answer to personal messages - use the forums instead.
0 Kudos
balkris
Xilinx Employee
Xilinx Employee
2,277 Views
Registered: ‎08-01-2008

Please make sure you are using supported OS
Microsoft Windows Support
• Windows 7 SP1 Professional (64-bit), English/Japanese.
• Windows 10 Professional Creators Update (64-bit), English/Japanese.
Linux Support
• Red Hat Enterprise Workstation/Server 7.2 and 7.3 (64-bit)
• Red Hat Enterprise Workstation 6.6, 6.7, 6.8, and 6.9 (64-bit)
• SUSE Linux Enterprise 11.4 and 12.2 (64-bit)
• Cent OS 7.2 and 7.3 (64-bit)
• Cent OS 6.7, 6.8, and 6.9 (64-bit)
• Ubuntu Linux 16.04.2 LTS (64-bit)

You may try running design on alteranate supported OS. I saw some of the customers seeing this issue on Windows OS.
Thanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
richard12345
Visitor
Visitor
2,269 Views
Registered: ‎01-19-2018

Hi hbucher,

 

Thank you very much for your reply.

 

Please find the actual code as attachment.

 

I am using Vivado 2017.4, both of windows and linux are this version.

 

 

 

Best regards

Richard

 

0 Kudos
richard12345
Visitor
Visitor
2,262 Views
Registered: ‎01-19-2018

Hi Balkrishan,

 

I am using Windows 10 Professional Creators Update (64-bit), English.

 

There are some log info as attachment, could you help to look at it.

 

There are some one who face the same issue, https://github.com/jingpu/Halide-HLS/issues/5

i follow his instruction, modify the file of 

C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\exception_ptr.h:134:13

and

C:/Xilinx/Vivado/2017.4/win64/tools/clang/bin\..\lib\clang\3.1/../../../include/c++/4.5.2\nested_exception.h:62:5

But i do not want to touch Vivado files, so i want to check whether there are other solutions without touch vivado files.

 

Best regards

Richard

 

 

Best regards

Richard

0 Kudos
hbucher
Scholar
Scholar
2,258 Views
Registered: ‎03-22-2016

@richard12345  This is not a normal HLS project. It has a custom makefile. It points to files external to the project that are not included. 

Can you create a new HLS project with a snippet of code that does not compile?

I cannot help much in the present case.

vitorian.com --- We do this for fun. Always give kudos. Accept as solution if your question was answered.
I will not answer to personal messages - use the forums instead.
0 Kudos
richard12345
Visitor
Visitor
2,237 Views
Registered: ‎01-19-2018

Hi hbucher,

 

i have reorganize the code, you can simply do make in windows os, after you set vivado settings64.bat.

 

Then you will see the error.

 

Thank you again.

BR

Richard

 

 

0 Kudos
stefanoribes
Contributor
Contributor
1,213 Views
Registered: ‎07-25-2016

Hi,

The workaround I found for Vivado 2018.3 on Windows 10 is to manually edit some Vivado files.

  • C:\Xilinx\Vivado\2018.3\win64\tools\clang\include\c++\4.5.2\exception_ptr.h : added the following small definition at the top of the file, as suggested here.
#ifndef _EXCEPTION_PTR_H
#define _EXCEPTION_PTR_H

#ifdef __clang__
    class type_info;
#endif

[...]
  •  C:\Xilinx\Vivado\2018.3\win64\tools\clang\include\c++\4.5.2\nested_exception.h : modified two lines, 110 and 122, as follows (suggested by the error message):
// __throw_with_nested(_Ex&&, const nested_exception* = 0) // original
    __throw_with_nested(_Ex&&, const nested_exception*) // modified

I don't know if this is breaking anything else in particular, but it seems to work flawlessly now.

Best,

Stefano