Pedro Rosa <[EMAIL PROTECTED]> writes:
> The src.rpm fails building when linking the libgcj lib. It produces:
>
> .libs/libgcj.so: undefined reference to 'LPR1'
> .libs/libgcj.so: undefined reference to 'LPR0'
> .libs/libgcj.so: undefined reference to 'LPR3'
> .libs/libgcj.so: undefined reference to 'LPR24'
> .libs/libgcj.so: undefined reference to 'LPR2'
> .libs/libgcj.so: undefined reference to 'LPR5'
> .libs/libgcj.so: undefined reference to 'LPR6'
> .libs/libgcj.so: undefined reference to 'LPR9'
> .libs/libgcj.so: undefined reference to 'LPR7'
> .libs/libgcj.so: undefined reference to 'LPR17'
> .libs/libgcj.so: undefined reference to 'LPR8'
> .libs/libgcj.so: undefined reference to 'LPR10'
>
> Sincerly I could not find where these references are coming from.
I had this hassle the other day. After many hours of digging, it seems
that it comes from...... the "-mcpu=pentiumpro" option given to gcc for
C++ code :-((.
Try to disable this option and see if it fixes (99.99% sure).
We'll see if we definitely remove this option, or we try to find a fix to
the compiler.
> Meanwhile there seems to be a patch concerning libgcj inside the source
> (on spec it is marked as patch12). However the patch, is in fact, a
> shell script.
>
> Apart from the java section it seems that there are several problems on
> building the packages. One of them, color-gcc package doesn't build. It
> drops with the statement:
>
> "objdump: ($RPM_BUILD_ROOT)/usr/bin/colorgcc : File format not
> recognized"
This `objdump' stuff is not a failing condition.
Try to issue "rpm -bi --short-circuit" and you'll see that it probably
misses some files (color-gcc probably, you said it).
--
Guillaume Cottenceau -- Distribution Developer for MandrakeSoft
http://www.mandrakesoft.com/~gc/
