Re: [PATCH] auto-generate libgcc.h

Hello Vladimir, Vladimir 'phcoder' Serbinenko wrote: rubisher wrote: Vladimir 'phcoder' Serbinenko wrote: Robert Millan wrote: This should be a much cleaner option than maintaining libgcc.h by hand. Only tested on sparc, but it should also cast out the build problems on powerpc. 1) Does

Re: [PATCH] auto-generate libgcc.h

rubisher wrote: > Vladimir 'phcoder' Serbinenko wrote: >> Robert Millan wrote: >>> This should be a much cleaner option than maintaining libgcc.h by >>> hand. Only >>> tested on sparc, but it should also cast out the build problems on >>> powerpc. >>> >>> >> 1) Doesn't work in cross-compiler en

Re: [PATCH] auto-generate libgcc.h

Vladimir 'phcoder' Serbinenko wrote: Robert Millan wrote: This should be a much cleaner option than maintaining libgcc.h by hand. Only tested on sparc, but it should also cast out the build problems on powerpc. 1) Doesn't work in cross-compiler environment. You confused CC and TARGET_CC

Re: [PATCH] auto-generate libgcc.h

Robert Millan wrote: > This should be a much cleaner option than maintaining libgcc.h by hand. Only > tested on sparc, but it should also cast out the build problems on powerpc. > > 1) Doesn't work in cross-compiler environment. You confused CC and TARGET_CC 2) Symbols don't get included into s

[PATCH] auto-generate libgcc.h

This should be a much cleaner option than maintaining libgcc.h by hand. Only tested on sparc, but it should also cast out the build problems on powerpc. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's t