On Sat, Aug 16, 2008 at 5:52 PM, Cristi Magherusan
<[EMAIL PROTECTED]> wrote:
> Okay, That workaround is really working ;) but is this a good fix on the
> long run? Why wouldn't gcc just let those include files where they
> belong?
limits.h is fixed up header so it belongs in include-fixed.
-- Pi
Hello,
On Sat, 2008-08-16 at 21:32 +0300, Cristi Magherusan wrote:
> On Sat, 2008-08-16 at 18:21 +, Joseph S. Myers wrote:
> > On Sat, 16 Aug 2008, Cristi Magherusan wrote:
> >
> > > Hello,
> > >
> > > It seems that gcc-4.3.1 has limits.h in the include-fixed directory,
> > > instead of the
On Sat, 2008-08-16 at 18:21 +, Joseph S. Myers wrote:
> On Sat, 16 Aug 2008, Cristi Magherusan wrote:
>
> > Hello,
> >
> > It seems that gcc-4.3.1 has limits.h in the include-fixed directory,
> > instead of the include one.
> > This breaks uclibc compilation.
> > What could be done to fix th
On Sat, 16 Aug 2008, Cristi Magherusan wrote:
> Hello,
>
> It seems that gcc-4.3.1 has limits.h in the include-fixed directory,
> instead of the include one.
> This breaks uclibc compilation.
> What could be done to fix this?
Use uClibc trunk revision 22067 or later.
--
Joseph S. Myers
[EMAIL
Hello,
It seems that gcc-4.3.1 has limits.h in the include-fixed directory,
instead of the include one.
This breaks uclibc compilation.
What could be done to fix this?
Best regards,
Cristi.
--
Ing. Cristi Măgherușan,
Universitatea Tehnică din Cluj-Napoca
Centrul de Comunicații "Pusztai Kalman
