Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
Yes, replace the snprintf() with _snprinf() solve the problem... 2012/1/12 Kai Tietz : > 2012/1/11 niXman : >> 2012/1/11 Ozkan Sezer : >>> On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: 2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz > wrote: >> Hmm, >

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
2012/1/12 Kai Tietz : > 2012/1/11 niXman : >> 2012/1/11 Ozkan Sezer : >>> On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: 2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz > wrote: >> Hmm, >> >> I assume this issue is caused by current 2.0 branch. It w

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Kai Tietz
2012/1/11 niXman : > 2012/1/11 Ozkan Sezer : >> On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: >>> 2012/1/11 Ozkan Sezer : On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz wrote: > Hmm, > > I assume this issue is caused by current 2.0 branch. It would be > really good if Ozk

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: >> 2012/1/11 Ozkan Sezer : >>> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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

Re: [Mingw-w64-public] Cygwin mingw64-i686-gcc-4.5.3-4: -Wformat warnings broken in C++

2012-01-11 Thread Christian Franke
JonY wrote: > On 1/6/2012 04:42, Kai Tietz wrote: >> 2012/1/5 Christian Franke: >>> [Originally sent to Cygwin mailing list] >>> >>> When printf/scanf functions from MinGW runtime are selected via >>> __USE_MINGW_ANSI_STDIO, then format string checking is broken. This only >>> affects the C++ compi

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Ozkan Sezer
On Wed, Jan 11, 2012 at 9:57 PM, niXman wrote: > 2012/1/11 Ozkan Sezer : >> On Wed, Jan 11, 2012 at 11:19 AM, Kai Tietz wrote: >>> 2012/1/11 Ozkan Sezer : On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz wrote: > Hmm, > > I assume this issue is caused by current 2.0 branch. It

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: >> 2012/1/11 Ozkan Sezer : >>> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 11:19 AM, Kai Tietz wrote: >> 2012/1/11 Ozkan Sezer : >>> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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/wc

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Ozkan Sezer
On Wed, Jan 11, 2012 at 9:51 PM, niXman wrote: > 2012/1/11 Ozkan Sezer : >> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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. >>

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread niXman
2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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 > b

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Ozkan Sezer
On Wed, Jan 11, 2012 at 11:19 AM, Kai Tietz wrote: > 2012/1/11 Ozkan Sezer : >> On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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.

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Kai Tietz
2012/1/11 Ozkan Sezer : > On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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 > b

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Ozkan Sezer
On Wed, Jan 11, 2012 at 11:02 AM, Kai Tietz 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 b

Re: [Mingw-w64-public] bad reloc address 0x20 in section '.eh_frame'

2012-01-11 Thread Kai Tietz
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. Kai 2012/1/11 niXman : > Hi list! > > At the next build of MinGW encountered this error: > E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o)