kidok / protobuf

Automatically exported from code.google.com/p/protobuf
0 stars 0 forks source link

Failed to build 2.5.0, on Win7, Cygwin, MSVS 2012 express #608

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Unpacked Zip, read readme.txt, opted for ./configure approach
(tried the MSVS IDEsolution but that failed too)

2. Launched Cygwin as admin 
3. Ran ./configure

What is the expected output? What do you see instead?

It seemed to be doing well until ....

checking dynamic linker characteristics... Win32 link.exe
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... cl.exe -E
checking whether the cl.exe linker (/Apps/Cygwin/bin/ld) supports shared 
libraries... yes
checking for cl.exe option to produce PIC... -DDLL_EXPORT -DPIC
checking if cl.exe PIC flag -DDLL_EXPORT -DPIC works... yes
checking if cl.exe static flag  works... yes
checking if cl.exe supports -c -o file.obj... no
checking if cl.exe supports -c -o file.obj... (cached) no
checking if we can lock with hard links... yes
checking whether the cl.exe linker (/Apps/Cygwin/bin/ld) supports shared librari
es... yes
checking dynamic linker characteristics... Win32 link.exe
checking how to hardcode library paths into programs... immediate
checking for python... :
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... no
checking whether pthreads work with -pthreads... no
checking whether pthreads work with -mthreads... no
checking for the pthreads library -lpthread... no
checking whether pthreads work with --thread-safe... no
checking whether pthreads work with -mt... no
checking for pthread-config... no
./configure: line 15628: sort: No such file or directory
./configure: line 15625: sed: No such file or directory
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/gtest-config
config.status: creating build-aux/config.h
config.status: build-aux/config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
./configure: line 18260: sort: No such file or directory
./configure: line 18257: sed: No such file or directory
./configure: line 19527: sort: No such file or directory
./configure: line 19524: sed: No such file or directory

Both sort and sed work on this machine.

I did notice that a Makefile was created so I ran make..... it generated:

protobuf-2.5.0> make
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /users/ae0371t/ProtocolBuffers/pr
otobuf-2.5.0/missing --run autoheader)
D:\users\ae0371t\bin\m4.exe:stdin:1: exit status out of range: `-1'
D:\users\ae0371t\bin\m4.exe:stdin:1: exit status out of range: `-1'
D:\users\ae0371t\bin\m4.exe:stdin:1: exit status out of range: `-1'
D:\users\ae0371t\bin\m4.exe: cannot set debug file `/tmp/acZu10fv/traces': No su
ch file or directory
D:\users\ae0371t\bin\m4.exe: cannot open /usr/share/autoconf/autoconf.m4f: No su
ch file or directory
autoconf: tracing failed
make: *** [config.h.in] Error 1

What version of the product are you using? On what operating system?

PB 2.5.0, on Win7, Cygwin, MSVS 2012 C++ Express (64 bit cross compile), Intel 
FORTRAN 14. (yes I know FORTRAN isn't used, but it does affect the env)

Please provide any additional information below.

I far prefer to use compilers via the command line, call me old school. But I 
did try to use the SLN files. They came up as "2010" not 2012, but I tried to 
build anyway. No luck ....

Thanks for any insight...

Original issue reported on code.google.com by Ce.slate...@gmail.com on 19 Feb 2014 at 6:46

GoogleCodeExporter commented 9 years ago
Guess I should have tried a clean build from a new download, I was using a 
2.5.0 package that I had run VS 2008 on, a clean build seems to kinda sorta 
worked we shall see.

I will update on it's ultimate success/failure

Original comment by Ce.slate...@gmail.com on 20 Feb 2014 at 2:33