From alexandre.chaboche at trixell-thalesgroup.com Fri Jan 22 03:05:44 2021 From: alexandre.chaboche at trixell-thalesgroup.com (CHABOCHE Alexandre) Date: Fri Jan 22 03:10:05 2021 Subject: [xsde-users] Build warning due to incompatible wchar_t size. Message-ID: <377e47eeeba7479eb02899ec2d8754ad@trixell-thalesgroup.com> Hello, I have a VxWorks 7 project using the libxsde and when I build it I have the following warning message : "libxsde.a(genx.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail". Until now I was only a user of this library, I never built it but this error make me think that may be I will have to rebuild it in the way to get the good wchar_t size configured. So my question is if it's possible to configure it during the library build? Best regards [Trixell] Alexandre CHABOCHE Embedded Software Engineer TRIXELL 460, rue du Pommarin 38430 Moirans - France www.trixell.com -------------- next part -------------- A non-text attachment was scrubbed... Name: OutlookEmoji-Trixell92b94ab0-90f5-4822-bbfe-19f1824a7137.png Type: image/png Size: 2517 bytes Desc: OutlookEmoji-Trixell92b94ab0-90f5-4822-bbfe-19f1824a7137.png Url : https://codesynthesis.com/pipermail/xsde-users/attachments/20210122/c36d6372/OutlookEmoji-Trixell92b94ab0-90f5-4822-bbfe-19f1824a7137.png From boris at codesynthesis.com Fri Jan 22 05:52:33 2021 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Jan 22 05:56:46 2021 Subject: [xsde-users] Build warning due to incompatible wchar_t size. In-Reply-To: <377e47eeeba7479eb02899ec2d8754ad@trixell-thalesgroup.com> References: <377e47eeeba7479eb02899ec2d8754ad@trixell-thalesgroup.com> Message-ID: Hi Alexandre, CHABOCHE Alexandre writes: > I have a VxWorks 7 project using the libxsde and when I build it I > have the following warning message : "libxsde.a(genx.o) uses 2-byte > wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t > values across objects may fail". That's strange: I looked through the recent source code of genx and it does not use wchar_t anywhere. Which version of XSD/e are you using? > Until now I was only a user of this library, I never built it but > this error make me think that may be I will have to rebuild it in > the way to get the good wchar_t size configured. So my question is > if it's possible to configure it during the library build? My guess is that libxsde.a was built with an older version of the compiler and a simple rebuild with the same version (and options) that you are using to build your application should help. Best regards, Boris From alexandre.chaboche at trixell-thalesgroup.com Fri Jan 22 05:59:19 2021 From: alexandre.chaboche at trixell-thalesgroup.com (CHABOCHE Alexandre) Date: Fri Jan 22 06:03:41 2021 Subject: [xsde-users] Build warning due to incompatible wchar_t size. In-Reply-To: References: <377e47eeeba7479eb02899ec2d8754ad@trixell-thalesgroup.com>, Message-ID: <910a0cc01afd42de98b3b497ea6cdabe@trixell-thalesgroup.com> Hello Boris, Thank you for your response. I'm using the V3.0.0 The rebuild can be the solution because I encounter this issue will I'm updating my VxWorks. And in the new version of VxWorks 7 the compiler is LLVM. I didn't see this compiler on the supported list on your site. Do you know if it's possible to compile the library with this new compiler? Best regards, Alexandre From boris at codesynthesis.com Fri Jan 22 06:36:45 2021 From: boris at codesynthesis.com (Boris Kolpackov) Date: Fri Jan 22 06:40:58 2021 Subject: [xsde-users] Build warning due to incompatible wchar_t size. In-Reply-To: <910a0cc01afd42de98b3b497ea6cdabe@trixell-thalesgroup.com> References: <377e47eeeba7479eb02899ec2d8754ad@trixell-thalesgroup.com> <910a0cc01afd42de98b3b497ea6cdabe@trixell-thalesgroup.com> Message-ID: CHABOCHE Alexandre writes: > The rebuild can be the solution because I encounter this issue will > I'm updating my VxWorks. And in the new version of VxWorks 7 the > compiler is LLVM. I didn't see this compiler on the supported list > on your site. Do you know if it's possible to compile the library > with this new compiler? Yes, I don't expect there to be any issues with Clang. From alexandre.chaboche at trixell-thalesgroup.com Wed Jan 27 05:34:25 2021 From: alexandre.chaboche at trixell-thalesgroup.com (CHABOCHE Alexandre) Date: Wed Jan 27 05:39:02 2021 Subject: [xsde-users] Build libxsde with clang Message-ID: Hello, I'm currently following the advice of Boris K. about a warning I have when I use my current built libxsde with the last VxWorks 7 release (SR660) and trying to rebuild the library with this new VxWorks environement (clang). I have set the build option and now I' meeting the following error during the build: "make[2]: *** [../../build/c/rules.make:11: c/expat/xmlparse.o] Error 1 make[2]: *** Waiting for unfinished jobs.... clang: ?[0;1;31merror: ?[0mcannot specify -o when generating multiple output files?[0m make[2]: *** [../../build/c/rules.make:11: c/expat/xmlrole.o] Error 1 make[2]: Leaving directory 'D:/app/Data/3131/XmlParser_working/xsde-3.0.0-i686-windows/libxsde/xsde' make[1]: *** [makefile:7: xsde] Error 2 make[1]: Leaving directory 'D:/app/Data/3131/XmlParser_working/xsde-3.0.0-i686-windows/libxsde' make: *** [makefile:10: libxsde] Error 2 " Can anybody help me with this error and firstly understand it? Best Regards Alexandre From boris at codesynthesis.com Wed Jan 27 06:07:07 2021 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Jan 27 06:11:38 2021 Subject: [xsde-users] Build libxsde with clang In-Reply-To: References: Message-ID: CHABOCHE Alexandre writes: > clang: error: cannot specify -o when generating multiple output files Can you re-try the build with -j 1 and show the command line that triggers this error? From alexandre.chaboche at trixell-thalesgroup.com Wed Jan 27 06:30:39 2021 From: alexandre.chaboche at trixell-thalesgroup.com (CHABOCHE Alexandre) Date: Wed Jan 27 06:35:16 2021 Subject: [xsde-users] Build libxsde with clang In-Reply-To: References: , Message-ID: <496d8ce29b8d4927a62740c04514ed6b@trixell-thalesgroup.com> Here is the command line with -J1 specified: "make[2]: Entering directory 'D:/app/Data/3131/XmlParser_working/xsde-3.0.0-i686-windows/libxsde/xsde' generating config.h here clang -I.. -O2 -target armv7a-none-eabi -msoft-float -mno-implicit-float -fno-builtin -fansi-escape-codes -D__vxworks -D__VXWORKS__ -D__ELF__ -D_HAVE_TOOL_XTORS -nostdlibinc -nostdinc++ -ftls-model=local-e xec -fno-builtin -fno-strict-aliasing -D_USE_INIT_ARRAY -mllvm -two-entry-phi-node-folding-threshold=2 -mno-implicit-float -MD -MP -mlong-calls -DCPU=_VX_ARMARCH7 -DTOOL_FAMILY=llvm -DTOOL=llvm -D_WRS_KERNEL -D _VSB_CONFIG_FILE=-I D:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h -DARMEL -U__USER_LABEL_PREFIX__ -D__USER_LABEL_PREFIX__= -D__ARM_NEON__ -DZEVAL -DSDHC_STORAGE-ID:\app\Data\3131\WS_ Branch_SP2R5_upgradeVXWorks\VSB\share\h -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\system -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\public -ID:\app\Data\3131\WS_Branch_SP2R5 _upgradeVXWorks\VSB\share\h\public -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\usr\h\public -fexceptions -c c/expat/xmlparse.c -o c/expat/xmlparse.o clang: ?[0;1;31merror: ?[0mcannot specify -o when generating multiple output files?[0m make[2]: *** [../../build/c/rules.make:11: c/expat/xmlparse.o] Error 1 make[2]: Leaving directory 'D:/app/Data/3131/XmlParser_working/xsde-3.0.0-i686-windows/libxsde/xsde' make[1]: *** [makefile:7: xsde] Error 2 make[1]: Leaving directory 'D:/app/Data/3131/XmlParser_working/xsde-3.0.0-i686-windows/libxsde' make: *** [makefile:10: libxsde] Error 2" ________________________________ De : Boris Kolpackov Envoy? : mercredi 27 janvier 2021 12:07 ? : CHABOCHE Alexandre Cc : xsde-users@codesynthesis.com Objet : Re: [xsde-users] Build libxsde with clang CHABOCHE Alexandre writes: > clang: error: cannot specify -o when generating multiple output files Can you re-try the build with -j 1 and show the command line that triggers this error? From boris at codesynthesis.com Wed Jan 27 08:34:14 2021 From: boris at codesynthesis.com (Boris Kolpackov) Date: Wed Jan 27 08:38:42 2021 Subject: [xsde-users] Build libxsde with clang In-Reply-To: <496d8ce29b8d4927a62740c04514ed6b@trixell-thalesgroup.com> References: <496d8ce29b8d4927a62740c04514ed6b@trixell-thalesgroup.com> Message-ID: CHABOCHE Alexandre writes: > clang -I.. -O2 -target armv7a-none-eabi -msoft-float -mno-implicit-float -fno-builtin -fansi-escape-codes -D__vxworks -D__VXWORKS__ -D__ELF__ -D_HAVE_TOOL_XTORS -nostdlibinc -nostdinc++ -ftls-model=local-e > xec -fno-builtin -fno-strict-aliasing -D_USE_INIT_ARRAY -mllvm -two-entry-phi-node-folding-threshold=2 -mno-implicit-float -MD -MP -mlong-calls -DCPU=_VX_ARMARCH7 -DTOOL_FAMILY=llvm -DTOOL=llvm -D_WRS_KERNEL -D > _VSB_CONFIG_FILE=-I D:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h -DARMEL -U__USER_LABEL_PREFIX__ -D__USER_LABEL_PREFIX__= -D__ARM_NEON__ -DZEVAL -DSDHC_STORAGE-ID:\app\Data\3131\WS_ > Branch_SP2R5_upgradeVXWorks\VSB\share\h -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\system -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\public -ID:\app\Data\3131\WS_Branch_SP2R5 > _upgradeVXWorks\VSB\share\h\public -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\usr\h\public -fexceptions -c c/expat/xmlparse.c -o c/expat/xmlparse.o It's hard for me pin-point exactly where the issue is because the line seems to be broken-up/re-formatted (probably by your mail client), but I think the issue is here: -D_VSB_CONFIG_FILE=-I D:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h Should probably be: -D_VSB_CONFIG_FILE= -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h And potentially here: -DSDHC_STORAGE-ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\share\h Should probably be: -DSDHC_STORAGE -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\share\h My guess would be you have some mistakes in your config.make. From alexandre.chaboche at trixell-thalesgroup.com Wed Jan 27 09:45:20 2021 From: alexandre.chaboche at trixell-thalesgroup.com (CHABOCHE Alexandre) Date: Wed Jan 27 09:49:48 2021 Subject: [xsde-users] Build libxsde with clang In-Reply-To: References: <496d8ce29b8d4927a62740c04514ed6b@trixell-thalesgroup.com>, Message-ID: Thank you Boris your answer permit me to step forward. It was typo error in the config.make . ________________________________ De : Boris Kolpackov Envoy? : mercredi 27 janvier 2021 14:34:14 ? : CHABOCHE Alexandre Cc : xsde-users@codesynthesis.com Objet : Re: [xsde-users] Build libxsde with clang CHABOCHE Alexandre writes: > clang -I.. -O2 -target armv7a-none-eabi -msoft-float -mno-implicit-float -fno-builtin -fansi-escape-codes -D__vxworks -D__VXWORKS__ -D__ELF__ -D_HAVE_TOOL_XTORS -nostdlibinc -nostdinc++ -ftls-model=local-e > xec -fno-builtin -fno-strict-aliasing -D_USE_INIT_ARRAY -mllvm -two-entry-phi-node-folding-threshold=2 -mno-implicit-float -MD -MP -mlong-calls -DCPU=_VX_ARMARCH7 -DTOOL_FAMILY=llvm -DTOOL=llvm -D_WRS_KERNEL -D > _VSB_CONFIG_FILE=-I D:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h -DARMEL -U__USER_LABEL_PREFIX__ -D__USER_LABEL_PREFIX__= -D__ARM_NEON__ -DZEVAL -DSDHC_STORAGE-ID:\app\Data\3131\WS_ > Branch_SP2R5_upgradeVXWorks\VSB\share\h -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\system -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\krnl\h\public -ID:\app\Data\3131\WS_Branch_SP2R5 > _upgradeVXWorks\VSB\share\h\public -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\usr\h\public -fexceptions -c c/expat/xmlparse.c -o c/expat/xmlparse.o It's hard for me pin-point exactly where the issue is because the line seems to be broken-up/re-formatted (probably by your mail client), but I think the issue is here: -D_VSB_CONFIG_FILE=-I D:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h Should probably be: -D_VSB_CONFIG_FILE= -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\h\config\vsbConfig.h And potentially here: -DSDHC_STORAGE-ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\share\h Should probably be: -DSDHC_STORAGE -ID:\app\Data\3131\WS_Branch_SP2R5_upgradeVXWorks\VSB\share\h My guess would be you have some mistakes in your config.make.