Re: [Mingw-w64-public] Object file install type
I changed that at one point. I forget why :( I'll look into it and change it back if that makes the most sense. On Sat, Feb 20, 2010 at 8:46 AM, Doug Semler dougsem...@gmail.com wrote: I notice that the crt .o and .a files are installed as scripts rather than data, which causes their file mode to be installed as executable (in a cross compile environment) Is there a specific reason for this? It seems to me that files such as crt32_SCRIPTS, lib32_SCRIPTS, etc should actually be crt32_DATA, lib32_DATA, etc, as these are not SCRIPTS (targets that are executable), but built DATA (static linker input files) Or am I missing something (as in behavior in an msys/cygwin/win32 type environment)? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Object file install type
On Sat, Feb 20, 2010 at 9:53 AM, NightStrike nightstr...@gmail.com wrote: I changed that at one point. I forget why :( I'll look into it and change it back if that makes the most sense. On Sat, Feb 20, 2010 at 8:46 AM, Doug Semler dougsem...@gmail.com wrote: I notice that the crt .o and .a files are installed as scripts rather than data, which causes their file mode to be installed as executable (in a cross compile environment) Is there a specific reason for this? It seems to me that files such as crt32_SCRIPTS, lib32_SCRIPTS, etc should actually be crt32_DATA, lib32_DATA, etc, as these are not SCRIPTS (targets that are executable), but built DATA (static linker input files) Or am I missing something (as in behavior in an msys/cygwin/win32 type environment)? Well an FYI I have it locally patched and it (seems :)) to work properly on a cross-compiler build install. Not saying that it would work in a win32 environment though. To me, it's really an annoyance more than anything else, but maybe it's because I'm more pedantic (read anal) about things like that :) -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
