Hi,
I made a binary rpm from sources'rpm of syslog-ng-3.5.4.1 For a rhel 6.x.
I had two issues :
1_ removing things I don't want or doesn't compile as geoip and others
2_ backporting to an old filesystem < 3.
Recent syslog-ng are made for a rhel's filesystem v3.x, where rhel 6.x is un v2.x
In short and from memory, it simply moves /lib to /usr/lib and same For /bin.
I had to set some variable on my spec file and remove dependency to filesystem v3.x.
Variables are like :
Prefix=/
Libdir=/lib
Execdir=/bin
In holidays, I am away from keyboard. So all this is only pointing a direction for you and from memory.
Regards, Nicolas.
<jrhendri@roadrunner.com> writes:
> RHEL 5:
> I have installed json-c & redis-stable which provides these libraries:
>
> ./redis-stable/deps/hiredis/hiredis.h
> ./redis-stable/deps/hiredis/libhiredis.a
>
> and created links here to try and get around issues:
> /usr/lib/hiredis
> /usr/lib/hiredis/libhiredis.a
> /usr/include/hiredis
> /usr/include/hiredis/hiredis.h
>
[...]
> Make fails here:
>
> CC modules/redis/modules_redis_libredis_la-redis-grammar.lo
> CC modules/redis/modules_redis_libredis_la-redis.lo
> CC modules/redis/modules_redis_libredis_la-redis-parser.lo
> CCLD modules/redis/libredis.la
> /usr/bin/ld: cannot find -lhiredis
> collect2: ld returned 1 exit status
> make[2]: *** [modules/redis/libredis.la] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> [n0142566@VDDP13E-F1A47ED syslog-ng-3.5.4.1]$
Can you run make with a V=1 parameter? That will tell us all the
parameters it passes to gcc when compiling and linking. The problem is
likely that the library is not on the search path, and for some reason,
we don't put it there either.
Running with V=1 should reveal what the issue is, more clearly.
--
|8]
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq