Synopsis - Issue Tracker

Neil via synopsis issue tracker wrote:

> c) running with -v on ctype.h gives lots of info, perhaps most important being:
>  ucpp -I/usr/local/include -I/usr/lib/gcc-lib/x86_64-linux/3.3.5/include -I/usr/include
> The /usr/lib/... patch is not installed within the chroot, so something is wrong there. All of my (recent) config/build/install commands were in the chroot and prefixed with linux32 (just in case), and a simple 'gcc -v' gives a first line of:
> Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs
> ...so something is being automagically picked - wrongly :(
> I looked in the file you mentioned and it is all x86-64 references. Something is looking at the cpu rather than the runtime?

Can you remove the emulator file and try again ?
I think I know what happens: the emulator file is a keeps an entry for each compiler
it finds, and it doesn't distinguish between 'gcc when run in chroot' and 'gcc native'.
The 'gcc' entry in your emulator file may stem from a run without chroot, and synopsis
now picks it up (wrongly) while in the chroot environment.

If that's the case I have to think about an alternative solution, as the compiler's
name (with absolute path) is clearly not enough to distinguish.
At least I should document this situation as something to be aware of, or avoid.