This is the mail archive of the
mailing list for the GCC project.
RE: can't run C compiled programs
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Mohamed Boukaa'" <mohamed dot boukaa at int-evry dot fr>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Tue, 16 May 2006 15:30:00 +0100
- Subject: RE: can't run C compiled programs
On 16 May 2006 15:15, Mohamed Boukaa wrote:
> Dave Korn wrote:
>> On 16 May 2006 12:12, Mohamed Boukaa wrote:
>>> checking for C compiler default output file name... a.out
>>> checking whether the C compiler works... configure: error: cannot run C
>>> compiled programs. If you meant to cross compile, use `--host'.
>>> See `config.log' for more details.
>>> --->Also when I compile a simple program by myself I got :
>>> ~ $ ./testaz
>>> bash: ./testaz: Permission denied
>>> However the portage is working fine , it can compile C and c++ programs
>> What happens if you "chmod a+x ./testaz"? You may have your UMASK set
> It gives the same thing, my umask is set at 022 .
> Has it something to do with the udpate of gcc from 3.4.4 to 3.4.5 ( any
> library issue) , I returned to 3.4.4 and the problem remains.
It should not be a problem. Every gcc version X.Y.* should remain
compatible, so all compilers from 3.4.* series should not cause any
If portage is working, perhaps you have more than one compiler/version
installed? What does "file ./testaz" say? Can you find out which one portage
is using and how it invokes it? Does portage have different path settings
when it runs?
Can't think of a witty .sigline today....