2010/3/21 Ozkan Sezer <seze...@gmail.com>:
> On Sun, Mar 21, 2010 at 7:21 PM, NightStrike <nightstr...@gmail.com> wrote:
>> Well, this is a problem, yes. It only affects the multilib builds,
>> though, which don't really work anyway without a lot of effort. And
>> this will all be fixed for 4.6, o we won't need to worry about it.
>>
>> If users really want it, though, I can rework things to exclude 32-bit
>> entirely. It's just a little messy in Makefile.am.
>>
>> On Sun, Mar 21, 2010 at 12:24 PM, Doug Semler <dougsem...@gmail.com> wrote:
>>> Quick question:
>>>
>>> Are you sure you want to disable the leading underscore on the 32bit side
>>> with
>>> the --disable-leading-underscore and multilib? Looking at it (without
>>> testing
>>> it, that is), it doesn't seem to me that it is appropriate...
>
> I think the flag really should be added to the lib64
> versions in the makefiles. Otherwise things would
> go far messier the may think of.
I agree, that it maybe gets for x86 much messier. And if possible, it
would be better to have this underscoring just active for x64.
> Besides that, there really is no way to tell the user
> as to how the crt was actually compiled. If there
> were a config header installed from within the crt
> build, maybe..
Hmm, for what this header should be? I see the issue that an user
can't see directly by which option for underscoring the crt was built,
but for this a header makes also no sense. To detect this a call of nm
reveals, if underscoring was active or not.
I don't think that we should introduce for this something in
configure. The header itself aren't affected, as they are checking the
underscoring mode of gcc directly.
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Download Intel® 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
