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

Re: Need to trace a script on mips/mipsel

On Wed, Sep 18, 2002 at 02:55:00PM +0200, Florian Lohoff wrote:
> On Wed, Sep 18, 2002 at 02:17:32PM +0200, Yann Dirson wrote:
> > There is still a problem with autodetection of pic/non-pic mixing in
> > bigloo for mips/mipsel.
> You cant mix pic/non-pic on mips/mipsel. Due to this the whole userspace
> is PIC.

That's what we're trying to detect at configure-time.  However, a
simple test of building a non-pic shlib and linking a program with it
does succeed.  Relevant lines from the trace are:

+ gcc -c /tmp/actestydirson-lib1.c -o actestydirson-lib1.o
+ gcc -c /tmp/actestydirson-lib2.c -o actestydirson-lib2.o
+ ld -shared -o /tmp/actestydirson.so actestydirson-lib1.o actestydirson-lib2.o -lc -lm
+ gcc -o /tmp/Xactestydirson /tmp/actestydirson.c /tmp/actestydirson.so
+ /tmp/Xactestydirson

This test is apparently sufficient on ia64, but for some reason it
does not fail on mipsel (and surely on mips as well).

The simple code provided by upstream does not explicitely call any
libc function, so I even added a call to printf to check, but that did
not change anything.

Anyone understand why it works, and what should be tested for instead ?

For those willing to take a closer look, the invocation is:

sh -x ./autoconf/ccpic2 --user=${USER} --tmp=/tmp --cc=gcc --cpicflags=-fPIC --cflags= --ldopt=-shared

The package is bigloo 2.5b-2, diff/dsc are still in incoming.

Yann Dirson <Yann.Dirson@fr.alcove.com>                 http://www.alcove.com/
Technical support manager                Responsable de l'assistance technique
Senior Free-Software Consultant          Consultant senior en Logiciels Libres
Debian developer (dirson@debian.org)                        Développeur Debian

Reply to: