-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.10.2013 06:32, asmwarrior wrote:
> On 2013-10-3 9:50, asmwarrior wrote:
>> I'm not sure the failure reason of detecting expat library in gdb.
> OK, I find the reason.
>
> There is another GCC in my system's PATH variable. Though the mouted /ming
On 2013-10-3 9:50, asmwarrior wrote:
> I'm not sure the failure reason of detecting expat library in gdb.
OK, I find the reason.
There is another GCC in my system's PATH variable. Though the mouted /mingw has
the high precedence in the PATH, but the configure script wrongly detect gcc in
"anothe
On 2013-10-3 3:15, Yaakov (Cygwin/X) wrote:
> On 2013-10-02 13:55, LRN wrote:
>> On 02.10.2013 22:50, Alexey Pavlov wrote:
>>> 2013/10/2 LRN wrote:
(offtopic: it looks like a bug that gdb links to libexpat.a instead of
libexpat.dll.a)
>
> FWIW, this also affects libiconv and libintl when
FAQ entry added under Execution section
https://sourceforge.net/apps/trac/mingw-w64/wiki/FAQ
Answer added as
https://sourceforge.net/apps/trac/mingw-w64/wiki/Usable%20compiler%20executable
Correct, modify, or make clearer as you see fit. If you don't have edit
privileges reply to this thread an
On 10/3/2013 02:53, Vaibhav Sood wrote:
> Hi,
>
> This is a followup to my earlier question about Win8 touch APIs, I just
> wanted to know in general which Win 8 APIs (if any) are supported in the
> latest build of the mingw-64 project. The change list on the main web page
> says 'overall improved
2013/10/2 Daniel Goldman
> Background - I gcc compile a C curses program under ubuntu Linux, using
> ncurses. It works
> great. I also compile the curses program under DOS / xp, using pdcurses
> included with
> mingw. The DOS version works fine in production mode. But there are some
> problems: 1
On 2013-10-02 12:17, Daniel Goldman wrote:
> So my questions: Can anyone point me in right direction to set up mingw-64 so
> I can
> compile a C curses program under mingw-64, either directly compile under DOS,
> or
> preferably cross-compile on ubuntu linux to generate DOS executable? Any
> sug
On 2013-10-02 13:55, LRN wrote:
On 02.10.2013 22:50, Alexey Pavlov wrote:
2013/10/2 LRN wrote:
(offtopic: it looks like a bug that gdb links to libexpat.a instead of
libexpat.dll.a)
FWIW, this also affects libiconv and libintl when building with NLS.
Why it a bug? I'm build GDB with static
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.10.2013 22:50, Alexey Pavlov wrote:
> 2013/10/2 LRN
>> (offtopic: it looks like a bug that gdb links to libexpat.a instead of
>> libexpat.dll.a)
>
> Why it a bug? I'm build GDB with static libexpat very often.
>
Because nothing htere indicate
Hi,
This is a followup to my earlier question about Win8 touch APIs, I just
wanted to know in general which Win 8 APIs (if any) are supported in the
latest build of the mingw-64 project. The change list on the main web page
says 'overall improved Windows 8 API support' but I could not find any
doc
2013/10/2 LRN
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02.10.2013 20:39, asmwarrior wrote:
> > Hi, I'm using D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5 to build GDB
> under MSYS.
> >
> > I have manually download the iconv, zlib, expat, and build and install
> them to /mingw.
> > (
> It's "_time32", not "time32"
Oh, thanks!
--
Regards,
niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingwbuilds/
___
Another online I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.10.2013 22:20, niXman wrote:
> example:
> #include
> int main() {
> time_t t;
> time32(&t);
> }
>
> compiled with: gcc time.c -otime
>
> error: undefined reference to `time32'
>
> What I am doing wrongly?
It's "_time32", not "time32"
example:
#include
int main() {
time_t t;
time32(&t);
}
compiled with: gcc time.c -otime
error: undefined reference to `time32'
What I am doing wrongly?
--
October Webinars: Code for Performance
Free Intel webin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.10.2013 20:39, asmwarrior wrote:
> Hi, I'm using D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5 to build GDB under
> MSYS.
>
> I have manually download the iconv, zlib, expat, and build and install them
> to /mingw.
> (in fstab, I have a line: D:\
2013/10/2 asmwarrior
>
> Hi, I'm using D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5 to build GDB under
> MSYS.
>
> I have manually download the iconv, zlib, expat, and build and install them
> to /mingw.
> (in fstab, I have a line: D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5\mingw32
> /mingw)
>
> N
Background - I gcc compile a C curses program under ubuntu Linux, using
ncurses. It works
great. I also compile the curses program under DOS / xp, using pdcurses
included with
mingw. The DOS version works fine in production mode. But there are some
problems: 1) in
test mode some printf option
Ruben Van Boxem schreef op wo 02-10-2013 om 16:58 [+0200]:
> Hi,
>
> I just noticed there is an SVN tag for 3.0.1 but no tarball.
>
>
> Could one be uploaded please?
Hey Ruben,
Some days ago I also mentioned this on IRC:
sep 30 23:13:12 jon_y, is 3.0.1 already out? I see that
you tagged i
Hi, I'm using D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5 to build GDB under
MSYS.
I have manually download the iconv, zlib, expat, and build and install them to
/mingw.
(in fstab, I have a line: D:\mingw-builds\x32-4.8.1-posix-dwarf-rev5\mingw32
/mingw)
Now, I found that detecting expat librar
2013/10/2 Ozkan Sezer
> On 10/2/13, Ruben Van Boxem wrote:
> > Hi,
> >
> > I just noticed there is an SVN tag for 3.0.1 but no tarball.
> >
> > Could one be uploaded please?
>
> IIRC, its only difference is the change of state from alpha to stable,
> none of the other commits to 3.x branch seeme
On 10/2/13, Ruben Van Boxem wrote:
> Hi,
>
> I just noticed there is an SVN tag for 3.0.1 but no tarball.
>
> Could one be uploaded please?
IIRC, its only difference is the change of state from alpha to stable,
none of the other commits to 3.x branch seemed in the 3.0.1 tag
--
O.S.
Hi,
I just noticed there is an SVN tag for 3.0.1 but no tarball.
Could one be uploaded please?
Thanks,
Ruben
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
On Win8 64bit using the recent mingw-w64 binary toolchain
`x86_64-4.8.1-release-win32-seh-rt_v3-rev2.7z` to build vim from source, I
see the following errors due to mingw32-make behavior:
C:\Apps\vim-hg>gcc --version
gcc (rev2, Built by MinGW-W64 project) 4.8.1
...
C:\Apps\vim-hg\src>mingw32-make
23 matches
Mail list logo
