On Fri, 23 Nov 2012, Ken Takata wrote:
Can you compile a program just using pow()?
For example:
$ cat a.c
#include
int main()
{
return (int) pow(2, 3);
}
$ i686-pc-mingw32-gcc a.c (or gcc-3 -mno-cygwin a.c)
$ ./a; echo $?
8
Yes, this works fine.
--
Please avoid sending me
Hi Christian,
2012/11/23 Fri 11:50:49 UTC+9 Heptite:
> And yet I still get the undefined reference to _pow error, regardless
> of which version of gcc I use.
Hmm, strange.
The symbol _pow is usually defined in a library libmsvcrt.a which
is linked by default.
Can you compile a program just usin
Hi Bram,
Ken Takata wrote:
> Bram Moolenaar wrote:
> > Looking at Make_mvc.mak, the extra directories are only used when the
> > Ruby version is 1.9 or later. Not for 1.8.
>
> Oh, I didn't notice that.
> How about this patch?
And I think this is the same for Make_ming.mak.
Thanks,
Ken Takata
Hi Bram,
Bram Moolenaar wrote:
> Looking at Make_mvc.mak, the extra directories are only used when the
> Ruby version is 1.9 or later. Not for 1.8.
Oh, I didn't notice that.
How about this patch?
Thanks,
Ken Takata
--
You received this message from the "vim_dev" maillist.
Do not top-post! Typ
Ken Takata wrote:
> I think that Make_cyg.mak needs some additional include dirs for ruby 1.9.
> After applying the attached patch, I can compile with the following command:
>
> $ make -f Make_cyg.mak CC=gcc-3 CXX=g++-3 RUBY='/path/to/ruby1.9.3'
> RUBY_VER=19 RUBY_VER_LONG=1.9.1
>
> Using i68
On Thu, 22 Nov 2012, Ken Takata wrote:
I think that Make_cyg.mak needs some additional include dirs for
ruby 1.9.
After applying the attached patch, I can compile with the following command:
$ make -f Make_cyg.mak CC=gcc-3 CXX=g++-3 RUBY='/path/to/ruby1.9.3'
RUBY_VER=19 RUBY_VER_LONG=1.9.1
Hi,
I think that Make_cyg.mak needs some additional include dirs for ruby 1.9.
After applying the attached patch, I can compile with the following command:
$ make -f Make_cyg.mak CC=gcc-3 CXX=g++-3 RUBY='/path/to/ruby1.9.3'
RUBY_VER=19 RUBY_VER_LONG=1.9.1
Using i686-pc-mingw32-gcc instead of g
On Tue, 20 Nov 2012, Steve Hall wrote:
On Tue, Nov 20, 2012 at 4:53 PM, Christian J. Robinson
wrote:
I was able to get Make_ming.mak to compile a native Windows
gvim.exe using Cygwin's MinGW packages as long as I don't try to
include Ruby.
When I try to include Ruby I get the following er
On Tue, Nov 20, 2012 at 4:53 PM, Christian J. Robinson
wrote:
>
> I was able to get Make_ming.mak to compile a native Windows gvim.exe
> using Cygwin's MinGW packages as long as I don't try to include
> Ruby.
>
> When I try to include Ruby I get the following errors:
[...]
>
> I wonder if this wou
On Thu, 15 Nov 2012, Christian J. Robinson wrote:
I would like to note that I have /never/ been able to get
Make_ming.mak to work under Cygwin, although other people appear to
know the "magic incantations." If someone could give me a hint,
perhaps it would work where Make_cyg.mak now fails.
On Thu, 15 Nov 2012, Bram Moolenaar wrote:
gobj/eval.o:eval.c:(.text+0x70b7): undefined reference to `_pow'
collect2: ld returned 1 exit status
Make_cyg.mak:534: recipe for target `gvim.exe' failed
make: *** [gvim.exe] Error 1
Please send a message to the vim-dev maillist. It's probably
some
On Thursday, November 15, 2012 2:42:32 AM UTC-5, Heptite wrote:
> gcc-3 -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce
> -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG -DWINVER=0x0500 -D_WIN32_WINNT=0x0500
> -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl512.dll\" -DFEAT_PYTHON
> -DD
gcc-3 -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG
-DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl512.dll\"
-DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_RUBY -DDYNAM
13 matches
Mail list logo
