Re: [yocto] meta-mingw: unable to run executables on Windows
Ok, thanks. On Thu, Nov 15, 2018 at 6:48 AM Mark Hatle wrote: > > On 11/14/18 11:01 PM, Khem Raj wrote: > > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: > >> > >> On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle > >> wrote: > >>> > >>> On 11/14/18 9:54 AM, Mark Hatle wrote: > On 11/13/18 3:56 AM, Samuli Piippo wrote: > > Hi, > > > > I've just upgraded poky and meta-mingw layers from sumo to thud and as > > a result > > a lot of the executables in the toolchain no longer run correctly on > > Windows. > > Which version of windows? > > > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, > > gcc/g++ work > > fine on Windows 10, but ar, as, objdumb, and others hang for ~30 > > seconds and > > exit without any output. > > > > Has anyone else seen this? > > I've run a toolchain made on mingw after sumo, but before thud's > release. I'll > see if I can find a VM and give it a try later today. > >>> > >>> I'm running on Windows 7 for my testing (ya, I know old.. but it's what I > >>> got.) > >>> > >>> Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 > >>> = "" > > > > this will be effective just for SDK and native versions I hope, but in > > cases if we > > have this override also applicable for target then this fix is not > > correct. We have > > to keep using it for target builds. > > The mingw32 override is only present when building -nativesdk- mingw32 > software. > -Not- cross candian and similar. > > --Mark > > >>> > >>> I found that the SDK was not working properly here as well, but only > >>> binutils. > >>> The above seems to fix the issue. (You do have to rebuild your SDK.) > >> > >> I also saw this issue on Windows 7, and your described fix corrected > >> it (Thanks!). On the plus side, the automated SDK testing that I'm > >> working on discovered it as well (e.g. the tests failed because of > >> it), which means that the tests are working and should help prevent > >> issues like this in the future once I get it merged. > >> > >>> > --Mark > > >>> > >>> -- > >>> ___ > >>> yocto mailing list > >>> yocto@yoctoproject.org > >>> https://lists.yoctoproject.org/listinfo/yocto > >> -- > >> ___ > >> yocto mailing list > >> yocto@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On 11/14/18 11:01 PM, Khem Raj wrote: > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: >> >> On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle wrote: >>> >>> On 11/14/18 9:54 AM, Mark Hatle wrote: On 11/13/18 3:56 AM, Samuli Piippo wrote: > Hi, > > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > result > a lot of the executables in the toolchain no longer run correctly on > Windows. Which version of windows? > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, > gcc/g++ work > fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds > and > exit without any output. > > Has anyone else seen this? I've run a toolchain made on mingw after sumo, but before thud's release. I'll see if I can find a VM and give it a try later today. >>> >>> I'm running on Windows 7 for my testing (ya, I know old.. but it's what I >>> got.) >>> >>> Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 = >>> "" > > this will be effective just for SDK and native versions I hope, but in > cases if we > have this override also applicable for target then this fix is not > correct. We have > to keep using it for target builds. The mingw32 override is only present when building -nativesdk- mingw32 software. -Not- cross candian and similar. --Mark >>> >>> I found that the SDK was not working properly here as well, but only >>> binutils. >>> The above seems to fix the issue. (You do have to rebuild your SDK.) >> >> I also saw this issue on Windows 7, and your described fix corrected >> it (Thanks!). On the plus side, the automated SDK testing that I'm >> working on discovered it as well (e.g. the tests failed because of >> it), which means that the tests are working and should help prevent >> issues like this in the future once I get it merged. >> >>> --Mark >>> >>> -- >>> ___ >>> yocto mailing list >>> yocto@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/yocto >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
Didn't see it arrive, maybe it's lost in moderation? What list did you post it to? Ross On Thu, 15 Nov 2018 at 09:28, Samuli Piippo wrote: > > patch sent. > On Thu, 15 Nov 2018 at 11:17, Burton, Ross wrote: > > > > Good work! > > > > Can we have a patch from someone please? > > > > Ross > > > > On Thu, 15 Nov 2018 at 08:35, Samuli Piippo wrote: > >> > >> On Thu, 15 Nov 2018 at 07:01, Khem Raj wrote: > >> > > >> > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: > >> > > > >> > > On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle > >> > > wrote: > >> > > > > >> > > > On 11/14/18 9:54 AM, Mark Hatle wrote: > >> > > > > On 11/13/18 3:56 AM, Samuli Piippo wrote: > >> > > > >> Hi, > >> > > > >> > >> > > > >> I've just upgraded poky and meta-mingw layers from sumo to thud > >> > > > >> and as a result > >> > > > >> a lot of the executables in the toolchain no longer run correctly > >> > > > >> on Windows. > >> > > > > > >> > > > > Which version of windows? > >> > > > > > >> > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From > >> > > > >> that, gcc/g++ work > >> > > > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 > >> > > > >> seconds and > >> > > > >> exit without any output. > >> > > > >> > >> > > > >> Has anyone else seen this? > >> > > > > > >> > > > > I've run a toolchain made on mingw after sumo, but before thud's > >> > > > > release. I'll > >> > > > > see if I can find a VM and give it a try later today. > >> > > > > >> > > > I'm running on Windows 7 for my testing (ya, I know old.. but it's > >> > > > what I got.) > >> > > > > >> > > > Can you try adding the following to your conf/local.conf: > >> > > > GCCPIE_mingw32 = "" > >> > > >> > this will be effective just for SDK and native versions I hope, but in > >> > cases if we > >> > have this override also applicable for target then this fix is not > >> > correct. We have > >> > to keep using it for target builds. > >> > > >> > > > > >> > > > I found that the SDK was not working properly here as well, but only > >> > > > binutils. > >> > > > The above seems to fix the issue. (You do have to rebuild your SDK.) > >> > > > >> > > I also saw this issue on Windows 7, and your described fix corrected > >> > > it (Thanks!). On the plus side, the automated SDK testing that I'm > >> > > working on discovered it as well (e.g. the tests failed because of > >> > > it), which means that the tests are working and should help prevent > >> > > issues like this in the future once I get it merged. > >> > > > >> > >> bisect finished last night and the winner was: commit > >> 491082c56ce34f3fd644f8d4457ccd52af951087 > >> poky.conf: Enable security flags+pie by defaultEnable security > >> flags+pie by default > >> > >> Adding GCCPIE_mingw32 = "" fixes this also for Windows 10 > >> -- > >> ___ > >> yocto mailing list > >> yocto@yoctoproject.org > >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
patch sent. On Thu, 15 Nov 2018 at 11:17, Burton, Ross wrote: > > Good work! > > Can we have a patch from someone please? > > Ross > > On Thu, 15 Nov 2018 at 08:35, Samuli Piippo wrote: >> >> On Thu, 15 Nov 2018 at 07:01, Khem Raj wrote: >> > >> > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: >> > > >> > > On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle >> > > wrote: >> > > > >> > > > On 11/14/18 9:54 AM, Mark Hatle wrote: >> > > > > On 11/13/18 3:56 AM, Samuli Piippo wrote: >> > > > >> Hi, >> > > > >> >> > > > >> I've just upgraded poky and meta-mingw layers from sumo to thud and >> > > > >> as a result >> > > > >> a lot of the executables in the toolchain no longer run correctly >> > > > >> on Windows. >> > > > > >> > > > > Which version of windows? >> > > > > >> > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, >> > > > >> gcc/g++ work >> > > > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 >> > > > >> seconds and >> > > > >> exit without any output. >> > > > >> >> > > > >> Has anyone else seen this? >> > > > > >> > > > > I've run a toolchain made on mingw after sumo, but before thud's >> > > > > release. I'll >> > > > > see if I can find a VM and give it a try later today. >> > > > >> > > > I'm running on Windows 7 for my testing (ya, I know old.. but it's >> > > > what I got.) >> > > > >> > > > Can you try adding the following to your conf/local.conf: >> > > > GCCPIE_mingw32 = "" >> > >> > this will be effective just for SDK and native versions I hope, but in >> > cases if we >> > have this override also applicable for target then this fix is not >> > correct. We have >> > to keep using it for target builds. >> > >> > > > >> > > > I found that the SDK was not working properly here as well, but only >> > > > binutils. >> > > > The above seems to fix the issue. (You do have to rebuild your SDK.) >> > > >> > > I also saw this issue on Windows 7, and your described fix corrected >> > > it (Thanks!). On the plus side, the automated SDK testing that I'm >> > > working on discovered it as well (e.g. the tests failed because of >> > > it), which means that the tests are working and should help prevent >> > > issues like this in the future once I get it merged. >> > > >> >> bisect finished last night and the winner was: commit >> 491082c56ce34f3fd644f8d4457ccd52af951087 >> poky.conf: Enable security flags+pie by defaultEnable security >> flags+pie by default >> >> Adding GCCPIE_mingw32 = "" fixes this also for Windows 10 >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
Good work! Can we have a patch from someone please? Ross On Thu, 15 Nov 2018 at 08:35, Samuli Piippo wrote: > On Thu, 15 Nov 2018 at 07:01, Khem Raj wrote: > > > > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt > wrote: > > > > > > On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle > wrote: > > > > > > > > On 11/14/18 9:54 AM, Mark Hatle wrote: > > > > > On 11/13/18 3:56 AM, Samuli Piippo wrote: > > > > >> Hi, > > > > >> > > > > >> I've just upgraded poky and meta-mingw layers from sumo to thud > and as a result > > > > >> a lot of the executables in the toolchain no longer run correctly > on Windows. > > > > > > > > > > Which version of windows? > > > > > > > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From > that, gcc/g++ work > > > > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 > seconds and > > > > >> exit without any output. > > > > >> > > > > >> Has anyone else seen this? > > > > > > > > > > I've run a toolchain made on mingw after sumo, but before thud's > release. I'll > > > > > see if I can find a VM and give it a try later today. > > > > > > > > I'm running on Windows 7 for my testing (ya, I know old.. but it's > what I got.) > > > > > > > > Can you try adding the following to your conf/local.conf: > GCCPIE_mingw32 = "" > > > > this will be effective just for SDK and native versions I hope, but in > > cases if we > > have this override also applicable for target then this fix is not > > correct. We have > > to keep using it for target builds. > > > > > > > > > > I found that the SDK was not working properly here as well, but only > binutils. > > > > The above seems to fix the issue. (You do have to rebuild your SDK.) > > > > > > I also saw this issue on Windows 7, and your described fix corrected > > > it (Thanks!). On the plus side, the automated SDK testing that I'm > > > working on discovered it as well (e.g. the tests failed because of > > > it), which means that the tests are working and should help prevent > > > issues like this in the future once I get it merged. > > > > > bisect finished last night and the winner was: commit > 491082c56ce34f3fd644f8d4457ccd52af951087 > poky.conf: Enable security flags+pie by defaultEnable security > flags+pie by default > > Adding GCCPIE_mingw32 = "" fixes this also for Windows 10 > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On Thu, 15 Nov 2018 at 07:01, Khem Raj wrote: > > On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: > > > > On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle wrote: > > > > > > On 11/14/18 9:54 AM, Mark Hatle wrote: > > > > On 11/13/18 3:56 AM, Samuli Piippo wrote: > > > >> Hi, > > > >> > > > >> I've just upgraded poky and meta-mingw layers from sumo to thud and as > > > >> a result > > > >> a lot of the executables in the toolchain no longer run correctly on > > > >> Windows. > > > > > > > > Which version of windows? > > > > > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, > > > >> gcc/g++ work > > > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 > > > >> seconds and > > > >> exit without any output. > > > >> > > > >> Has anyone else seen this? > > > > > > > > I've run a toolchain made on mingw after sumo, but before thud's > > > > release. I'll > > > > see if I can find a VM and give it a try later today. > > > > > > I'm running on Windows 7 for my testing (ya, I know old.. but it's what I > > > got.) > > > > > > Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 > > > = "" > > this will be effective just for SDK and native versions I hope, but in > cases if we > have this override also applicable for target then this fix is not > correct. We have > to keep using it for target builds. > > > > > > > I found that the SDK was not working properly here as well, but only > > > binutils. > > > The above seems to fix the issue. (You do have to rebuild your SDK.) > > > > I also saw this issue on Windows 7, and your described fix corrected > > it (Thanks!). On the plus side, the automated SDK testing that I'm > > working on discovered it as well (e.g. the tests failed because of > > it), which means that the tests are working and should help prevent > > issues like this in the future once I get it merged. > > bisect finished last night and the winner was: commit 491082c56ce34f3fd644f8d4457ccd52af951087 poky.conf: Enable security flags+pie by defaultEnable security flags+pie by default Adding GCCPIE_mingw32 = "" fixes this also for Windows 10 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On Wed, Nov 14, 2018 at 8:08 PM Joshua Watt wrote: > > On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle wrote: > > > > On 11/14/18 9:54 AM, Mark Hatle wrote: > > > On 11/13/18 3:56 AM, Samuli Piippo wrote: > > >> Hi, > > >> > > >> I've just upgraded poky and meta-mingw layers from sumo to thud and as a > > >> result > > >> a lot of the executables in the toolchain no longer run correctly on > > >> Windows. > > > > > > Which version of windows? > > > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, > > >> gcc/g++ work > > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds > > >> and > > >> exit without any output. > > >> > > >> Has anyone else seen this? > > > > > > I've run a toolchain made on mingw after sumo, but before thud's release. > > > I'll > > > see if I can find a VM and give it a try later today. > > > > I'm running on Windows 7 for my testing (ya, I know old.. but it's what I > > got.) > > > > Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 = > > "" this will be effective just for SDK and native versions I hope, but in cases if we have this override also applicable for target then this fix is not correct. We have to keep using it for target builds. > > > > I found that the SDK was not working properly here as well, but only > > binutils. > > The above seems to fix the issue. (You do have to rebuild your SDK.) > > I also saw this issue on Windows 7, and your described fix corrected > it (Thanks!). On the plus side, the automated SDK testing that I'm > working on discovered it as well (e.g. the tests failed because of > it), which means that the tests are working and should help prevent > issues like this in the future once I get it merged. > > > > > > --Mark > > > > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On Wed, Nov 14, 2018 at 8:41 PM Mark Hatle wrote: > > On 11/14/18 9:54 AM, Mark Hatle wrote: > > On 11/13/18 3:56 AM, Samuli Piippo wrote: > >> Hi, > >> > >> I've just upgraded poky and meta-mingw layers from sumo to thud and as a > >> result > >> a lot of the executables in the toolchain no longer run correctly on > >> Windows. > > > > Which version of windows? > > > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, > >> gcc/g++ work > >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds > >> and > >> exit without any output. > >> > >> Has anyone else seen this? > > > > I've run a toolchain made on mingw after sumo, but before thud's release. > > I'll > > see if I can find a VM and give it a try later today. > > I'm running on Windows 7 for my testing (ya, I know old.. but it's what I > got.) > > Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 = "" > > I found that the SDK was not working properly here as well, but only binutils. > The above seems to fix the issue. (You do have to rebuild your SDK.) I also saw this issue on Windows 7, and your described fix corrected it (Thanks!). On the plus side, the automated SDK testing that I'm working on discovered it as well (e.g. the tests failed because of it), which means that the tests are working and should help prevent issues like this in the future once I get it merged. > > > --Mark > > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On 11/14/18 9:54 AM, Mark Hatle wrote: > On 11/13/18 3:56 AM, Samuli Piippo wrote: >> Hi, >> >> I've just upgraded poky and meta-mingw layers from sumo to thud and as a >> result >> a lot of the executables in the toolchain no longer run correctly on Windows. > > Which version of windows? > >> I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ >> work >> fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds and >> exit without any output. >> >> Has anyone else seen this? > > I've run a toolchain made on mingw after sumo, but before thud's release. > I'll > see if I can find a VM and give it a try later today. I'm running on Windows 7 for my testing (ya, I know old.. but it's what I got.) Can you try adding the following to your conf/local.conf: GCCPIE_mingw32 = "" I found that the SDK was not working properly here as well, but only binutils. The above seems to fix the issue. (You do have to rebuild your SDK.) > --Mark > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On 11/13/18 3:56 AM, Samuli Piippo wrote: > Hi, > > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > result > a lot of the executables in the toolchain no longer run correctly on Windows. Which version of windows? > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ > work > fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds and > exit without any output. > > Has anyone else seen this? I've run a toolchain made on mingw after sumo, but before thud's release. I'll see if I can find a VM and give it a try later today. --Mark -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On Tue, 13 Nov 2018 at 12:17, Burton, Ross wrote: > > On Tue, 13 Nov 2018 at 09:57, Samuli Piippo wrote: > > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > > result a lot of the executables in the toolchain no longer run correctly on > > Windows. > > > > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ > > work fine on Windows 10, but ar, as, objdumb, and others hang for ~30 > > seconds and exit without any output. > > > > Has anyone else seen this? > > I suspect we need to find a maintainer who actually uses meta-mingw > and can actually test it. Would you be willing to bisect thud to sumo > to identify where it breaks? I can try to setup some kind of automatic bisect run script to test this. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-mingw: unable to run executables on Windows
On Tue, 13 Nov 2018 at 09:57, Samuli Piippo wrote: > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > result a lot of the executables in the toolchain no longer run correctly on > Windows. > > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ > work fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds > and exit without any output. > > Has anyone else seen this? I suspect we need to find a maintainer who actually uses meta-mingw and can actually test it. Would you be willing to bisect thud to sumo to identify where it breaks? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-mingw: unable to run executables on Windows
Hi, I've just upgraded poky and meta-mingw layers from sumo to thud and as a result a lot of the executables in the toolchain no longer run correctly on Windows. I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ work fine on Windows 10, but ar, as, objdumb, and others hang for ~30 seconds and exit without any output. Has anyone else seen this? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
