- 06 Jan, 2018 2 commits
-
-
not-a-robot[bot] authored
569: Ibm aix fix r=badboy
-
Jan-Erik Rediger authored
Closes #422
-
- 05 Jan, 2018 5 commits
-
-
not-a-robot[bot] authored
568: Make XOPEN_SOURCE definition explicit per architecture r=badboy Fixes #441
-
Jan-Erik Rediger authored
Fixes #441
-
cdliuqiang@gmail.com authored
-
Jan-Erik Rediger authored
Fix "make install" on OpenBSD
-
Jan-Erik Rediger authored
Remove $(ARCH) expansion from the Makefile
-
- 28 Dec, 2017 1 commit
-
-
Dmitri Vorobiev authored
The Makefile checks validity of the compiler command in the CC variable by feeding the contents of that variable to the `type' utility. Some environments include compiler options in the CC variable such as architecture specific tuning flags. For such cases it is necessary to first strip everything except the command itself from the contents of the CC variable prior to checking the command with the type utility, which is what this patch is introducing. We use shell parameter expansion mechanism for this purpose. Signed-off-by:
Dmitri Vorobiev <dmitri.vorobiev@movial.com>
-
- 27 Dec, 2017 1 commit
-
-
Dmitri Vorobiev authored
Some compilation environments (such as Yocto) define the ARCH environment variable to indicate the target architecture. For such enviroments, hiredis build fails, because the expanded $(ARCH) variable in the Makefile gets erroneously interpreted as an argument to the `-ggdb' command line option during the compilation stage or as an input file name during the linking stage. This patch removes $(ARCH) expansions from the Makefile. This doesn't harm cross-compilation, the latter goes fine with the properly assigned CC environment variable. For native builds, this patch does not imply any changes. Signed-off-by:
Dmitri Vorobiev <dmitri.vorobiev@movial.com>
-
- 29 Nov, 2017 1 commit
-
-
Zach Shipko authored
-
- 07 Nov, 2017 2 commits
-
-
not-a-robot[bot] authored
554: build: do not assume that INSTALL is cp r=badboy INSTALL is supposed to be `install` in most of the cases which doesn't work with directories, but works perfectly with files. Don't do this assumption. Reported-by:
Jiří Vymazal <jvymazal@redhat.com> References: https://bugzilla.redhat.com/show_bug.cgi?id=1506251 Signed-off-by:
Igor Gnatenko <i.gnatenko.brain@gmail.com>
-
Jan-Erik Rediger authored
-
- 30 Oct, 2017 1 commit
-
-
Igor Gnatenko authored
INSTALL is supposed to be `install` in most of the cases which doesn't work with directories, but works perfectly with files. Don't do this assumption. Reported-by:
Jiří Vymazal <jvymazal@redhat.com> References: https://bugzilla.redhat.com/show_bug.cgi?id=1506251 Signed-off-by:
Igor Gnatenko <i.gnatenko.brain@gmail.com>
-
- 01 Sep, 2017 2 commits
-
-
Jan-Erik Rediger authored
correct spelling mistake
-
Edward Betts authored
-
- 15 Jul, 2017 3 commits
-
-
not-a-robot[bot] authored
533: Small fixes r=badboy
-
not-a-robot[bot] authored
524: Don't pass a negative value to __redisAsyncCommand if redisFormatSdsCommandArgv fails r=badboy 525: Fix compilation on FreeBSD 10.3 with default compiler r=badboy Given FreeBSD 10.3 with default compiler: > $ cc -v > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > Target: x86_64-unknown-freebsd10.3 Defining _XOPEN_SOURCE to 600 on the fixed line leads to the following errors: > cc -std=c99 -pedantic -c -O3 -fPIC -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb net.c > net.c:435:29: error: use of undeclared identifier 'AF_LOCAL' > if (redisCreateSocket(c,AF_LOCAL) < 0) > ^ > net.c:460:21: error: use of undeclared identifier 'AF_LOCAL' > sa.sun_family = AF_LOCAL; > ^ > 2 errors generated. > AF_LOCAL is defined in sys/socket.h within ifdef __BSD_VISIBLE. __BSD_VISIBLE could be defined in sys/cdefs.h, but it is never done if _XOPEN_SOURCE is defined. So on FreeBSD _XOPEN_SOURCE shouldn't be defined.
-
not-a-robot[bot] authored
523: Fix leak if setsockopt fails r=badboy
-
- 16 Jun, 2017 1 commit
-
-
Jan-Erik Rediger authored
Assert statement calls a function which has side effects
-
- 15 Jun, 2017 2 commits
- 17 May, 2017 1 commit
-
-
eldarko authored
-
- 15 May, 2017 2 commits
-
-
Frederik Deweerdt authored
-
Frederik Deweerdt authored
-
- 07 Apr, 2017 4 commits
-
-
Jan-Erik Rediger authored
redisLibeventCleanup will be leak
-
Jan-Erik Rediger authored
chore(CI): Skip installing Cygwin
-
Jan-Erik Rediger authored
-
Jan-Erik Rediger authored
Build error when make examples , patch with glib-2.0 positon move will solve.
-
- 28 Mar, 2017 1 commit
-
-
zfz authored
event_del can not free the "e->rev" and "e->wev",that will leak when reconnect the redis
-
- 22 Mar, 2017 2 commits
-
-
Jan-Erik Rediger authored
suppress gcc complaint
-
Ichito Nagata authored
-
- 23 Jan, 2017 1 commit
-
-
Jan-Erik Rediger authored
Fix __redisSetErrorFromErrno() can not get error string.
-
- 30 Dec, 2016 1 commit
-
-
Jin Qing authored
snprintf() may change errno.
-
- 09 Dec, 2016 3 commits
-
-
not-a-robot authored
using new version libevent
-
not-a-robot authored
Prevented uv adapter from calling write when context has been freed The `redisLibuvPoll` function can be called with both the `UV_READABLE` and `UV_WRITABLE` flags set at the same time. Calling `redisAsyncHandleRead` can lead to a disconnect and the context being cleaned up/freed. If this happens then `redisAsyncHandleWrite` should not be called otherwise memory read/write errors and duplicate freeing will occur. These changes prevent this from happening by having the `redisLibuvCleanup` callback indicate that the context has been cleaned. This is done indirectly by setting the context to a null pointer, maybe someone can come up with a cleaner way.
-
Jan-Erik Rediger authored
Closes #471
-
- 04 Nov, 2016 1 commit
-
-
Jan-Erik Rediger authored
Remove trailing comma in redisConnectionType enum
-
- 25 Oct, 2016 1 commit
-
-
Donald Whyte authored
Remove trailing comma in last value of `redisConnectionType` enum. This causes a compiler warning on Solaris compilers. I'd like to build this on Solaris with `-Werror`. However, due to the trailing comma, I cannot do that. This PR removes the trailing comma, which should prevent it causing compiler warnings on any architecture.
-
- 09 Oct, 2016 1 commit
-
-
Trustfarm-heart authored
In case of some glib-2.0 linker error , make examples can't link with glib2.0, in this case -lglib-2.0 to after includes and move to last will solve the issues.
-
- 19 Sep, 2016 1 commit
-
-
Paul Scott authored
-