cancel
Showing results for 
Search instead for 
Did you mean: 
Participant
Participant
172 Views
Registered: ‎08-11-2019

‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?

Jump to solution

我在ubuntu16.04  vitis2019.2版本中运行Vitis_Accel_Examples/cpp_kernels/dataflow_stream 例程,Emulation-Hardware,Hardware均顺利通过,但Emulation-Software未通过,提示以下错误:

ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/bits/stdint-intn.h:27:conflicting declaration ‘typedef __int64_t int64_t’
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:43:‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:44:‘__int_least16_t’ does not name a type; did you mean ‘__int16_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:45:‘__int_least32_t’ does not name a type; did you mean ‘__int32_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:46:‘__int_least64_t’ does not name a type; did you mean ‘__int64_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:49:‘__uint_least8_t’ does not name a type; did you mean ‘__uint8_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:50:‘__uint_least16_t’ does not name a type; did you mean ‘__uint16_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:51:‘__uint_least32_t’ does not name a type; did you mean ‘__uint32_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:52:‘__uint_least64_t’ does not name a type; did you mean ‘__uint64_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:101:‘__intmax_t’ does not name a type; did you mean ‘__intptr_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/stdint.h:102:‘__uintmax_t’ does not name a type; did you mean ‘__uint64_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:58:‘::int_least8_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:59:‘::int_least16_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:60:‘::int_least32_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:61:‘::int_least64_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:63:‘::intmax_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:76:‘::uint_least8_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:77:‘::uint_least16_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:78:‘::uint_least32_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:79:‘::uint_least64_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/cstdint:81:‘::uintmax_t’ has not been declared
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:511:‘uint_least16_t’ does not name a type; did you mean ‘uint_fast16_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:584:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:587:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:592:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:592:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:595:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:599:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:608:‘uint_least32_t’ does not name a type; did you mean ‘uint_fast32_t’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:681:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:684:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:689:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:689:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:692:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/include/c++/8.2.0/bits/char_traits.h:696:‘int_type’ does not name a type; did you mean ‘off_type’?
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/bits/cpu-set.h:42:conflicting declaration ‘typedef struct cpu_set_t cpu_set_t’
ERROR: [v++ 17-1309] Gcc: /tools/Xilinx/Vitis/2019.2/gnu/aarch64/lin/aarch64-linux/aarch64-linux-gnu/libc/usr/include/errno.h:37:conflicting declaration of ‘int* __errno_location()’ with ‘C’ linkage
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:63:‘__DECL_SIMD_cosf32’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:65:‘__DECL_SIMD_sinf32’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:109:‘__DECL_SIMD_logf32’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:63:‘__DECL_SIMD_cosf64’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:65:‘__DECL_SIMD_sinf64’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:109:‘__DECL_SIMD_logf64’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:63:‘__DECL_SIMD_cosf128’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:65:‘__DECL_SIMD_sinf128’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:109:‘__DECL_SIMD_logf128’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:116:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:151:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:157:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:176:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:196:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:52:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:63:‘__DECL_SIMD_cosf32x’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:65:‘__DECL_SIMD_sinf32x’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:77:‘_Mdouble_END_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:98:‘_Mdouble_BEGIN_NAMESPACE’ does not name a type
ERROR: [v++ 17-1309] Gcc: /usr/include/x86_64-linux-gnu/bits/mathcalls.h:109:‘__DECL_SIMD_logf32x’ does not name a type
INFO: [v++ 17-14] Message 'v++ 17-1309' appears 100 times and further instances of the messages will be disabled.
ERROR: [v++ 60-398] gcc failed
ERROR: [v++ 60-626] Kernel link failed to complete
ERROR: [v++ 60-703] Failed to finish linking

 

请问是什么问题导致的错误呢,我该如何避免这个问题?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Xilinx Employee
Xilinx Employee
29 Views
Registered: ‎07-16-2008

Re: ‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?

Jump to solution

这是Edge Platform在Ubuntu上的已知问题,在2020.1版本修复。

2019.2版本在CentOS上无此问题。

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos
3 Replies
Highlighted
Visitor
Visitor
109 Views
Registered: ‎03-05-2020

Re: ‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?

Jump to solution

我遇到了相同的问题,请问您是否解决了,可以分享一下吗

0 Kudos
Highlighted
Participant
Participant
88 Views
Registered: ‎08-11-2019

Re: ‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?

Jump to solution
我还没解决,在等待回复……如果我想出方法了,会随时更新答案的!
0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
30 Views
Registered: ‎07-16-2008

Re: ‘__int_least8_t’ does not name a type; did you mean ‘__intptr_t’?

Jump to solution

这是Edge Platform在Ubuntu上的已知问题,在2020.1版本修复。

2019.2版本在CentOS上无此问题。

-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos