On Wed, Jan 11, 2012 at 9:57 PM, niXman <[email protected]> wrote: > 2012/1/11 Ozkan Sezer <[email protected]>: >> On Wed, Jan 11, 2012 at 11:19 AM, Kai Tietz <[email protected]> wrote: >>> 2012/1/11 Ozkan Sezer <[email protected]>: >>>> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz <[email protected]> >>>> wrote: >>>>> Hmm, >>>>> >>>>> I assume this issue is caused by current 2.0 branch. It would be >>>>> really good if Ozkan could catch-up the stdio/wchar fixes from trunk >>>>> for it. >>>> >>>> why do this happens at all which had never happened >>>> before: nixman: is this with v2.0x branch crt/headers >>>> or with the trunk? >>> >>> Well, I changed on trunk scope for function being static unused. This >>> fixes that issue, as for force-inline we lack a function-pointer, >>> which is used by some projects. >> >> I see, >> >> Can you provide some pointers as to which revisions, etc >> needs applying to stable branches: I'm a bit behind these >> days >> >>> Btw I added same forwarder mechanism >>> to vsnprintf/snprintf in trunk. Additionally I checked in yesterday a >>> fix for XP's msvcrt without vsnprintf export by forwarding it to >>> _vsnprintf. This forwarding causes the requirement to have binutils >>> with '==' directive support in .def files. Last recent binutils >>> releases should already provide this feature. >>> >> >> We never had (v)snprintf exports without the leading >> underscore in the stable branches's def files, so this is >> a trunk thing: should I add them to the stable branches? >> >>> >>>>> >>>>> Kai >>>>> >>>>> 2012/1/11 niXman <[email protected]>: >>>>>> Hi list! >>>>>> >>>>>> At the next build of MinGW encountered this error: >>>>>> E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o):domain.c:(.text+0x1088): >>>>>> undefined reference to `snprintf' >>>> [snip] >>>> >>>> I wonder: if libcloog is using snprintf() and not _snprintf(), >>>> why are they not fixing it and we are tearing ourselves apart? >>>> Are they aware of the issues? >>> >>> I would assume so, and I assume also they won't take care about it >>> pretty much as snprintf is POSIX style. I admit it would be better if >>> people would use the leading-underscore variant instead, but well ... >>> >>> Kai >> >> The issue reporter should at least notify them. > I.e. I have to send them information about this bug?
If they are using snprintf() for windows instead of _snprintf() then it is a bug on their end, and since you found it by a failed linkage you shoulyd report it to them > In what form? > I cannot know that. by whatever bug reporting mechanism they provide -- O.S. ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
