Stephen Marsh <mars7017@xxxxxxxxxxxx> writes: > Shouldn't the compiler be included in the gcc package repository? Is > this an issue of a dependency that wasn't installed or an error in the > repo? I don't know if the error is in the package repository you are using or somewhere else. I don't even know what OS you are using. From what you showed, it appears that the compiler is there but the assembler is not. The compiler and assembler are typically in different packages, and I would assume that the compiler package normally requires the assembler package. On GNU systems the assembler is normally part of a binutils package. Ian > From: Ian Lance Taylor <iant@xxxxxxxxxx> > To: Stephen Marsh <mars7017@xxxxxxxxxxxx> > Cc: gcc-help@xxxxxxxxxxx > Sent: Fri, Jan 21, 2011 4:16 pm > Subject: Re: ./configure error: failed program was: /* confdefs.h. */ > > > Stephen Marsh <mars7017@xxxxxxxxxxxx> writes: > >> GCC version 4.41 installed through SliTaz Package manager won't allow >> me to install / build autocutsel ( http://www.nongnu.org/autocutsel/ ) >> . Any suggestions why the failed program confdefs.h isn't working? > > As the installation instruction say, we recommend against running > ./configure. Run configure in an empty directory instead. I recommend > unpacking the sources from scratch to avoid confusion left behind by > ./configure. > > However, your specific problem is this: > >> configure:2156: gcc conftest.c >&5 >> gcc: error trying to exec 'as': execvp: No such file or directory > > You don't have an assembler on your path. Your compiler--the one you > are going to use to build gcc--doesn't work. > > Ian > >
