Re: Strange problem building Package commonc++

Hi,

I wrote:
> Hi,
>
> Marian Aldenhövel wrote:
> > Hi,
> >
> > > Is this problem still open  or did you solve it in the meantime?
> >
> > I did not solve it, but it is not hurting me either.
> >
> > It turned out that the program I was porting did require, but not
> > in any way use commonc++ features. So I was able to remove the
> > requirement instead.
> >
> > So if it's just me, don't bother.
>
> I just check with a PPC cross build and commonc++ indeed cross
> builds with glibc, butnot with uclibc.
>
> I take a look, maybe it's fixable within some minutes.
>
> Have a nice Sunday,
Took some time to figure out what mysterious macro expansion stuff is 
going on there,
Actually the error you hit was caused by not detecting strerror_r suport 
in the configure
script which caused commonc++ to define it's own macro, which further 
influenced and
messed up some strerror_r wrapping inherited from glibc into uclibc 
(actually the header
files are mostly indentical between glibc and uclibc, ...).

I had to work around another build error related to no high-res timers 
being implemented
yet by the release version of uclibc.

Both issues are now taken care of in the T2 commonc++ package by 
pre-filling the
config.cache.

Committed revision 29604.

Yours,

--
 René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
 http://exactcode.de | http://t2-project.org | http://rene.rebe.name



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
lists@xxxxxxxxxxxxxx with a subject of: unsubscribe t2