- Oct 14, 2008
-
-
Yang Tse authored
Remove -b from debug-enabled configuration, as Tiny C might have been built without the memory and bounds checker support.
-
Yang Tse authored
Better disable following warnings when cross-compiling with a gcc older than 3.0, to avoid warnings from third party system headers: -Wmissing-declarations -Wmissing-prototypes -Wunused -Wshadow
-
Daniel Stenberg authored
-
Yang Tse authored
-
Yang Tse authored
-
Yang Tse authored
-
- Oct 13, 2008
-
-
Daniel Stenberg authored
options don't succeed in opening the target file etc. Detected by coverity.com
-
Daniel Stenberg authored
coverity.com
-
Daniel Stenberg authored
has already been dereferenced so it is bound to be valid. Pointed out to us by coverity.com
-
Dan Fandrich authored
-
Yang Tse authored
-
Yang Tse authored
Disable following warnings when cross-compiling with a gcc older than 3.0, to avoid warnings from third party system headers: -Wmissing-prototypes -Wunused -Wshadow
-
Yang Tse authored
-
Yang Tse authored
And on the other hand a message after setsockopt() certainly must use SOCKERRNO.
-
Yang Tse authored
Do not enable -pedantic when cross-compiling with a gcc older than 3.0, to avoid warnings from third party system headers.
-
- Oct 12, 2008
-
-
Yang Tse authored
-
Yang Tse authored
Highest warning level is double -A, next is single -A. Due to the big number of warnings these trigger on third party header files it is impratical for us to use any of them here. If you want them simply define it in CPPFLAGS.
-
Dan Fandrich authored
-
Dan Fandrich authored
use the startup of the IPv6 test server as a substitute check for this).
-
- Oct 11, 2008
- Oct 10, 2008
-
-
Dan Fandrich authored
-
Yang Tse authored
-
Patrick Monnerat authored
_ Update RPG binding accordingly. _ Fix new options comments.
-
Yang Tse authored
-
Yang Tse authored
-
Yang Tse authored
2) Disable SGI remark: controlling expression is constant
-
Yang Tse authored
-
Dan Fandrich authored
-
Yang Tse authored
-
Yang Tse authored
Due to the HP-UX socklen_t issue it is insane to use the +w1 warning level. It generates more than 1100 warnings on socklen_t related statements. Until the issue is somehow fixed we will just use the +w2 warning level.
-
Yang Tse authored
-
Yang Tse authored
-
- Oct 09, 2008
-
-
Dan Fandrich authored
-
Daniel Stenberg authored
because the struct is declared on the stack and not all members are used so we could just as well make struct with only struct members we actually need.
-
Dan Fandrich authored
for spotting it).
-
Yang Tse authored
-