Re: [Libunwind-devel] [PATCH 10/19] Change test-varargs to check libunwind backtracing

[Tommi Rantala]

2012/9/11 Arun Sharma <address@hidden>:
> On Mon, Sep 10, 2012 at 5:16 PM, Cody P Schafer <address@hidden> wrote:
>> This breaks building test-varargs for me with
>>
>> /bin/sh ../libtool --tag=CC   --mode=link gcc  -ggdb -g3 -fexceptions -Wall
>> -Wsign-compare   -o test-varargs test-varargs.o
>> libtool: link: gcc -ggdb -g3 -fexceptions -Wall -Wsign-compare -o
>> test-varargs test-varargs.o
>> test-varargs.o: In function `b':
>> /root/cody/build.libunwind/tests/../../libunwind/tests/test-varargs.c:22:
>> undefined reference to `unw_backtrace'
>> collect2: ld returned 1 exit status
>>
>> During build on ppc64.

Hi Cody, I fail to understand why the test is not linking against
libunwind. Looking at tests/Makefile.am, many other tests are also
LDADD'ing $(LIBUNWIND_local), so I would assume you should see similar
failures e.g. with "test-async-sig" and "test-flush-cache". Does it
make any difference if you run something like "git clean -xdf ;
autoreconf -fiv" in your source dir, and build from a clean directory?

I'm unable to reproduce this, the test builds fine in native build
(x86_64), and various cross-builds, e.g. cross-PPC32 shows this:

address@hidden:/butter/git/libunwind-ppc/tests$ make test-varargs
depbase=`echo test-varargs.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
        powerpc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I../../libunwind/tests -I../include  -I../../libunwind/include
-D_GNU_SOURCE -DNDEBUG  -O2 -g -Wall -fexceptions -Wall -Wsign-compare
-MT test-varargs.o -MD -MP -MF $depbase.Tpo -c -o test-varargs.o
../../libunwind/tests/test-varargs.c &&\
        mv -f $depbase.Tpo $depbase.Po
/bin/bash ../libtool --tag=CC   --mode=link powerpc-linux-gnu-gcc  -O2
-g -Wall -fexceptions -Wall -Wsign-compare   -o test-varargs
test-varargs.o ../src/libunwind.la
libtool: link: powerpc-linux-gnu-gcc -O2 -g -Wall -fexceptions -Wall
-Wsign-compare -o .libs/test-varargs test-varargs.o
../src/.libs/libunwind.so
address@hidden:/butter/git/libunwind-ppc/tests$

> Are you configuring with UNW_REMOTE_ONLY by any chance?
>
> Tommi: if this is the problem, I think we should guard the test also
> the same way in tests/Makefile.am.
>
>  -Arun