Buildrump $CC -v test fails for pcc

[staalmannen]

The output if CC=pcc is:

ERROR:
Cannot run "pcc -v". Check that "pcc" is a compiler

trying pcc -v gives the following output:

$ pcc -v
pcc 1.0.0.RELEASE 20110221 for x86_64-unknown-linux-gnu, jens@Krypton
no input files

on my machine.

[anttikantee]

Does "pcc -dumpmachine" output anything sensible?

[staalmannen]

nope... unfortunately not:

$ pcc -dumpmachine
no input files
$ pcc -dumpspecs
no input files

[anttikantee]

Looks like it just needs to detect that "cc -v" comes from pcc and use an alternative parser to determine the target.

[staalmannen]

with this modification I get further in the build (pcc is nicely faster than both gcc and clang)

https://github.com/staalmannen/buildrump.sh/commit/82da03ed1106b902748011d534b235bf717fb36c

I keep this sepparate in an experimental branch for now. My solutions are most likely sub-optimal...

[anttikantee]

This might be a simpler expression for parsing the target: sed -n '/^pcc/s/.*for \([^,]*\).*/\1/p'

btw, test(1) can do string comparison, e.g. [ "a" = "b" ] returns false. But you probably want to check if the compiler thinks it's pcc (cc -v), not if the binary name is pcc.

[justincormack]

I think all these parsing issues are fixed, but there are some issues with pcc still referenced in #66 and alas Jens' fork seems to have disappeared.