In message <[email protected]>
          Chris Gransden <[email protected]> wrote:

> In article <[email protected]>,
>    John Tytgat <[email protected]> wrote:
> > In message <[email protected]>
> >           Chris Gransden <[email protected]> wrote:
> 
> > > In article <[email protected]>,
> > >    Frank de Bruijn <[email protected]> wrote:
> > > 
> > > > That's where I put it yesterday. Fetching the files for tcp-wrappers
> > > > wouldn't have worked correctly if I hadn't.
> > > 
> > > I've found the problem with tcp-wrappers. There's a newer version of
> > > 'signal.h' in trunk than in the 4.1.2 branch. You get get it from
> > > http://www.riscos.info/websvn/filedetails.php?repname=gccsdk&path=%2Ftrunk%2Fgcc4%2Frecipe%2Ffiles%2Fgcc%2Flibunixlib%2Finclude%2Fsignal.h.
> > >  It goes in
> > > 'cross/arm-unknown-riscos/include'.
> 
> > This advice might solve a build problem but if tcp-wrappers is really
> > using the siginfo_t feature, then you will have a problem at runtime.
> 
> It was just a workaround to get 'build-libs -a' to complete.

A very noble task. :-)

> The rest of
> the changes are part of r5568. Is it possible to apply these to the 4.1.2
> branch as well?

The branches/release_4_1_2 is a stable branch is in priniple only meant
to get bug fixes.  I'm not sure whether the siginfo_t changes can be
qualified as such.  Lee actually contributed this, so perhaps he can give
some insight how risky this change is.

John.
-- 
John Tytgat, in his comfy chair at home
[email protected]

_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Reply via email to