On 2010-04-18 at 14:15:34 [+0200], Andreas Färber <andreas.faerber@xxxxxx> wrote: > Am 17.04.2010 um 22:29 schrieb Ingo Weinhold: > > Unfortunately using either gcc without having set it as the current > > compiler (via setgcc) doesn't work ATM. > > Confirmed, with Matt's instructions during the gcc2 part of the build > I instead get: > > gcc: installation problem, cannot exec `cpp0': No such file or directory > > One difference is that instead of absolute paths {{{configure}}} > appears to generate relative paths for the non-set gcc, e.g. {{{.}}} > and {{{./include}}}. Replacing those with absolute paths does not > improve the situation. Is there already a ticket for that? I didn't > find one on a quick search. I don't think there's a ticket yet. There's a general problem with using the non-set gcc, which would require changes on the gcc side (cf. [1]). I haven't looked at or past that yet. CU, Ingo [1] http://dev.haiku-os.org/ticket/5518#comment:10