invalid variable name errors in cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, when I try to run my configure it complains about invalid variable names given to the script[1]. I tried to get the source of the problem, it seems the lines ~ *=*) ~ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='` ~# Reject names th

Re: invalid variable name errors in cygwin

Ralf Wildenhues schrieb: Hi Ralf, Interesting. Try adding `set -x' before and `set +x' after the parsing loop. Please report exact shell version used, the exact version of coreutils (expr), whether configure restarts under another shell (try `sh -x configure ...' to find that out: if it restar

Running a different linker

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hi list, I want to compile some microcontoroller code with autoconf/automake. The problem I have is that I must explicit call the linker, because the compiler is unable to link the code. Also the linker is split into two programs, which must be c

Configuring compilers for tatget and build

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hi all, is there any way to get configure detect a compiler for the build host and the target, so that on the build host can programs compiled and run to build some of the target source codes? My problem is that I need a compiler which is embedd