search for: limitx

...Shipman <dshipman at gmail.com> wrote: > I've just tried building r54494 on 64bit linux and had the same (no > include path) > error. Any idea what's happening here? > No. :-( Could you try Mike's suggestion? (Replicated here) Try adding: #define _GCC_LIMITS_H_ to limitx.h like so: #ifdef _GCC_NEXT_LIMITS_H +#define _GCC_LIMITS_H_ #include_next <limits.h> #undef _GCC_NEXT_LIMITS_H and then testing. A good test would do a -dM -E and seeing if everything is still defined and checking the testcase mentioned in the original email thread.

...: --- ./gsyslimits.h.~1~ 2006-11-26 12:31:50.000000000 -0800 +++ ./gsyslimits.h 2007-04-02 12:37:38.000000000 -0700 @@ -4,5 +4,3 @@ instead of this text. */ #define _GCC_NEXT_LIMITS_H /* tell gcc's limits.h to recurse */ -#include_next <limits.h> -#undef _GCC_NEXT_LIMITS_H --- ./limitx.h.~1~ 2006-11-26 12:31:48.000000000 -0800 +++ ./limitx.h 2007-04-02 13:51:40.000000000 -0700 @@ -1,12 +1,11 @@ /* This administrivia gets added to the beginning of limits.h if the system has its own version of limits.h. */ -/* We use _GCC_LIMITS_H_ because we want this not to match - any...

> to limitx.h like so: > > #ifdef _GCC_NEXT_LIMITS_H > +#define _GCC_LIMITS_H_ > #include_next <limits.h> > #undef _GCC_NEXT_LIMITS_H This fixes this problem for me on Ubuntu Hardy on x86-64. John

...t;> I've just tried building r54494 on 64bit linux and had the same (no >> include path) >> error. Any idea what's happening here? >> > No. :-( Could you try Mike's suggestion? (Replicated here) > > Try adding: > > #define _GCC_LIMITS_H_ > > to limitx.h like so: > > #ifdef _GCC_NEXT_LIMITS_H > +#define _GCC_LIMITS_H_ > #include_next <limits.h> > #undef _GCC_NEXT_LIMITS_H > > and then testing. A good test would do a -dM -E and seeing if > everything is still defined and checking the testcase mentioned in the > or...

Hi all, I'm having some trouble building llvm-gcc as of today, with and without bootstrap. The error I get is: /home/kooijman/src/llvm-gcc/obj/./gcc/xgcc -B/home/kooijman/src/llvm-gcc/obj/./gcc/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/ -B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem

Hi Matthijs, >> I did put in a hack, but it was horrible. It might be a good idea to >> test out Mike's suggestion to see if it's a better way of doing it. > I just tried building llvm-gcc without your hack, and it still works (even > without the fix Mike suggested). > > So, it seems that r54245 can be reverted again? > > I didn't test bootstrap, however,

I've just tried building r54494 on 64bit linux and had the same (no include path) error. Any idea what's happening here? Thanks, -David Shipman On Fri, Aug 8, 2008 at 6:12 AM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Matthijs, > >>> I did put in a hack, but it was horrible. It might be a good idea to >>> test out Mike's suggestion to see if

On Jul 30, 2008, at 11:35 PM, Bill Wendling wrote: > I think this error is due to these changes: Try adding: #define _GCC_LIMITS_H_ to limitx.h like so: #ifdef _GCC_NEXT_LIMITS_H +#define _GCC_LIMITS_H_ #include_next <limits.h> #undef _GCC_NEXT_LIMITS_H and then testing. A good test would do a -dM -E and seeing if everything is still defined and checking the testcase mentioned in the original email thread.

...gcc/i686-pc-mingw32/bin/ -B/c/Temp/msys-llvm-gcc/i686-pc-mingw32/lib/ -isystem /c/Temp/msys-llvm-gcc/i686-pc-mingw32/include -isystem /c/Temp/msys-llvm-gcc/i6 86-pc-mingw32/sys-include -dumpspecs > tmp-specs mv tmp-specs specs if true ; then \ cat ../../llvm-gcc4.2-2.6.source/gcc/limitx.h ../../llvm-gcc4.2-2.6.so urce/gcc/glimits.h ../../llvm-gcc4.2-2.6.source/gcc/limity.h > tmp-xlimits.h; \ else \ cat ../../llvm-gcc4.2-2.6.source/gcc/glimits.h > tmp-xlimits.h; \ fi mv tmp-xlimits.h xlimits.h echo | /c/Temp/msys-gcc-build/./gcc/xgcc -B/c/Temp/...

...tall//i686-pc-cygwin/bin/ > -B/llvm-gcc/../install//i686-pc-cygwin/lib/ > -isystem /llvm-gcc/../install//i686-pc-cygwin/include > -isystem /llvm-gcc/../install//i686-pc-cygwin/sys-include -dumpspecs > > tmp-specs > mv tmp-specs specs > if ; then \ > > cat ../../src/gcc/limitx.h ../../src/gcc/glimits.h ../../src/gcc/limity.h > tmp-xlimits.h; \ > else \ > cat ../../src/gcc/glimits.h > tmp-xlimits.h; \ > fi > make[1]: Leaving directory `/llvm-gcc/obj/gcc' > > I though it was ld error, first, and reinstalled it to clean 2.17 > instead...

If you're building llvm-gcc4, you don't need the runtime libraries, so I'd just stick with the "tools-only" build and declare success. If you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) However, the problem appears to be your PATH variable. In your path you have the following directory: C:/Program Files/Microsoft DirectX SDK (June

Hi! I'm trying to build LLVM under cygwin. I have the latest version of cygwin and CVS versions of llvm, llvm-test and llvm-gcc. make of tools only succeeded. make of frontend succeeded too but full make of llvm failed on crtend in llvm/runtime/GCCLibraries with the following message: llvm[0]: Compiling crtend.c for Debug build (bytecode) /bin/sh: -c: line 0: syntax error near unexpected

...-B/llvm-gcc/obj/gcc/ -B/llvm-gcc/../install//i686-pc-cygwin/bin/ -B/llvm-gcc/../install//i686-pc-cygwin/lib/ -isystem /llvm-gcc/../install//i686-pc-cygwin/include -isystem /llvm-gcc/../install//i686-pc-cygwin/sys-include -dumpspecs > tmp-specs mv tmp-specs specs if ; then \ cat ../../src/gcc/limitx.h ../../src/gcc/glimits.h ../../src/gcc/limity.h > tmp-xlimits.h; \ else \ cat ../../src/gcc/glimits.h > tmp-xlimits.h; \ fi make[1]: Leaving directory `/llvm-gcc/obj/gcc' I though it was ld error, first, and reinstalled it to clean 2.17 instead of cygwn experimental version. but th...