[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Cluster 3.0.0.rc3 release

On Wed, Jul 01, 2009 at 07:12:07PM +0200, Fabio M. Di Nitto wrote:
> Do you have a build log for the package? and could you send me the
> make/defines.mk in the build tree?
No, not from that build we're currently using. I can rebuild though. But
from our libccss modifications:

gcc -Wall -Wformat=2 -Wshadow -Wmissing-prototypes -Wstrict-prototypes
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings
-Wbad-function-cast -Wmissing-format-attribute -Wformat-security
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing
-Wmissing-declarations -O2 -ggdb3 -MMD
-D_FILE_OFFSET_BITS=64 -I/usr/include
-I/var/home/schmitz/3/redhat-cluster/common/liblogthread `xml2-config
--cflags` -I/usr/include   -c -o libccs.o
ar cru libccs.a libccs.o xpathlite.o fullxpath.o extras.o
ranlib libccs.a
gcc -shared -o libccs.so.3.0 -Wl,-soname=libccs.so.3 libccs.o
fullxpath.o extras.o  -L/usr/lib/corosync -lconfdb `xml2-config --libs`
ln -sf libccs.so.3.0 libccs.so
ln -sf libccs.so.3.0 libccs.so.3

> gcc versions and usual tool chain info.. maybe it's a gcc bug or maybe
> it's an optimization that behaves differently between debian and fedora.
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1'

$ ld -v
GNU ld (GNU Binutils for Debian)

$ dpkg -s libc6-dev
Package: libc6-dev
Status: install ok installed
Priority: optional
Section: libdevel
Installed-Size: 11072
Maintainer: GNU Libc Maintainers <debian-glibc lists debian org>
Architecture: amd64
Source: glibc
Version: 2.7-18
Replaces: man-db (<= 2.3.10-41), gettext (<= 0.10.26-1), ppp (<=
2.2.0f-24), libgdbmg1-dev (<= 1.7.3-24)
Provides: libc-dev
Depends: libc6 (= 2.7-18), linux-libc-dev
Recommends: gcc | c-compiler
Suggests: glibc-doc, manpages-dev
Conflicts: libstdc++2.10-dev (<< 1:2.95.2-15), gcc-2.95 (<< 1:2.95.3-8),
binutils (<< 2.17cvs20070426-1), libc-dev

> I have attached a small test case to simply test libccs. At this point I
> don't believe it's a problem in libfence. Could you please run it for me
> and send me the output? If the bug is in libccs this would start
> isolating it.
# ./testccs
Segmentation fault

# and if I prefer fullxpath over xpathlite:
# ./testccs
Segmentation fault

 -- Guido

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]