Bug#309986: gcc-4.0 build problems on powerpc

[Falk Hueffner <falk@debian.org>]

Roger Leigh <rleigh@whinlatter.ukfsn.org> writes:

> ./libtool: line 4696: /usr/bin/expr: Argument list too long
> using piecewise archive linking...
>
> This is while creating libgcj.a, so there may be some object files
> missed out of the ar command.  It's happening inside libtool.

The piecewise linking should take care of that.

> /home/rleigh/gcc/gcc-4.0-4.0.0/src/libobjc/thr.c:117: warning: 'noreturn' function does return
>
> Remove the noreturn attribute??

Rather, add one to objc_thread_exit. Not a real problem.

> ../../../src/boehm-gc/mark_rts.c: In function 'GC_approx_sp':
> ../../../src/boehm-gc/mark_rts.c:379: warning: function returns address of local variable
>
> That's never a good idea.

Not a problem either, this is just done to get the value of the stack
pointer.

> And there's a shlibs problem in a few packages, for example
>
> dh_shlibdeps -pgnat-4.0 -L libgnat-4.0 -l debian/libgnat-4.0/usr/lib
> dpkg-shlibdeps: warning: could not find path for ld.so.1
> dpkg-shlibdeps: warning: could not find any packages for  (ld.so.1)
> dpkg-shlibdeps: warning: unable to find dependency information for shared library ld (soname 1, path , dependency field Depends)
>
> $ cat /var/lib/dpkg/info/libc6.shlibs
> ld 1 libc6 (>= 2.3.2.ds1-21)
>
> Presumably, there's a binary linked incorrectly or a problem in the
> rules or the control file causing this.  Maybe something's assuming
> something i386-specific, like ld-linux.so.2, but I'm afraid I'm not at
> all familiar with the GCC packaging.

I don't know what to make of this either.

-- 
	Falk