tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Problems with distcc on earmv4

> Where is "gcc: error: c: No such file or directory" coming from? Any ideas,

Between this:

> distcc[6836] (dcc_scan_args) scanning arguments: gcc -fcommon -O2 -fPIC
> -D_FORTIFY_SOURCE=2 -DUNIX -o flops flops.c -lm -fPIC -D_FORTIFY_SOURCE=2
> -fstack-protector-strong
> -I/usr/pkgsrc/benchmarks/flops/work/.buildlink/include -pie

and this:

> distcc[6836] exec on localhost: gcc -fcommon -O2 -fPIC c -DUNIX -o flops
> flops.c -lm -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector-strong
> -I/usr/pkgsrc/benchmarks/flops/work/.buildlink/include -pie

the extra stray "c" gets introduced (after -O2the extra stray "c" gets
introduced (after -O2 -fPIC), and here it is still present:

> distcc[6836] (dcc_spawn_child) forking to execute: gcc -fcommon -O2 -fPIC c
> -DUNIX -o flops flops.c -lm -fPIC -D_FORTIFY_SOURCE=2
> -fstack-protector-strong
> -I/usr/pkgsrc/benchmarks/flops/work/.buildlink/include -pie

Maybe that helps you to pinpoint the issue.

___ "Buying carbon credits is a bit like a serial killer paying someone else to
\X/  have kids to make his activity cost neutral." -The BOFH

Attachment: signature.asc
Description: PGP signature

Home | Main Index | Thread Index | Old Index