codegooglecom / libproxy

Automatically exported from code.google.com/p/libproxy
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Build of libproxy-0.4.0 fails #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. make
2.
3.

What is the expected output? What do you see instead?
*** Building libproxy *** [35/59]
make
[  3%] Built target libmodman
[  9%] Built target builtin
[ 12%] Built target condition
[ 16%] Built target condition_one
[ 19%] Built target condition_two
[ 22%] Built target singleton
[ 25%] [ 29%] Built target builtin_one
Built target pxgconf
[ 32%] Built target singleton_one
[ 35%] Built target singleton_two
[ 38%] Built target sorted
[ 41%] Built target sorted_one
[ 48%] [ 48%] Built target symbol
Built target sorted_two
[ 51%] Built target symbol_one
[ 54%] [ 58%] Built target symbol_two
Built target symbollnk
[ 93%] Built target libproxy
[ 96%] Building CXX object
libproxy/CMakeFiles/config_gnome.dir/modules/config_gnome.cpp.o
[100%] Built target proxy
cc1plus: warnings being treated as errors
/home/muelli/vcs/gnome/libproxy-0.4.0/libproxy/modules/config_gnome.cpp: In
function ‘int popen2(const char*, FILE**, FILE**, pid_t*)’:
/home/muelli/vcs/gnome/libproxy-0.4.0/libproxy/modules/config_gnome.cpp:76:
error: ignoring return value of ‘int dup(int)’, declared with attribute
warn_unused_result
/home/muelli/vcs/gnome/libproxy-0.4.0/libproxy/modules/config_gnome.cpp:77:
error: ignoring return value of ‘int dup(int)’, declared with attribute
warn_unused_result
make[2]: ***
[libproxy/CMakeFiles/config_gnome.dir/modules/config_gnome.cpp.o] Error 1
make[1]: *** [libproxy/CMakeFiles/config_gnome.dir/all] Error 2
make: *** [all] Error 2

I expected it to compile fine

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

Please provide any additional information below.

Original issue reported on code.google.com by 4tmue...@gmail.com on 3 Jun 2010 at 10:08

GoogleCodeExporter commented 9 years ago
Please try a version later than 0.4.0, this issue is already resolved in 0.4.2.

Original comment by npmccallum@gmail.com on 4 Jun 2010 at 12:41