Re: [linuxsh-dev] Next change

[M. R. B. <mr...@0x...>]

* NIIBE Yutaka <gn...@m1...> on Fri, Sep 21, 2001:

> M. R. Brown wrote:
>  > Actually gcc 3.0.1 (latest official release) can bootstrap and build
>  > sh-linux.  It doesn't have the target specific "no multilib" support, so you
>  > can't build sh4-linux, but it still works without patches.  When I started
>  > working on an alternative to the current multilib scheme (i.e. completely
>  > disabling mulitlibs for the generic sh-linux target), I tested gcc 3.0.1
>  > *without* kaz's patches, and I was able to build and boot kernels just
>  > fine.
> 
> I've re-read the diff of gcc-sh-linux package.  I think that for use
> of shared library, the change of libgcc.a (of hidden) is required, at
> least.
> 

I and others have always been confused by the "hidden" patch.  What does it
do?  Why is it required?  I've build glibc without it, so it isn't required
for that build step - what other reasons are there?

> My point is, I don't think it is minimum set of patches, but it is OK
> for Debian bootstrap.  3.0.1 is not OK for whole build.
> 

If Debian wants to make that divergence and they support you, then cool (I
guess), but I speak for a few SH developers (not just sh-linux) that would
like to see mainline be *the* SH toolkit, and not rely on a fork (think
about it, if it were sanctioned by gcc it'd be it's own branch) to get
things done.

Hopefully the work done by MontaVista and kaz's continual patch submission
can help get us there.

M. R.