URL:
<http://savannah.gnu.org/support/?105544>
Summary: Selecting an alternative compiler for "make" to
use.
Project: Savannah Administration
Submitted by: peter_anderson
Submitted on: Tuesday 05/09/06 at 14:31
Category: None
Priority: 5 - Normal
Severity: 4 - Important
Status: None
Assigned to: None
Originator Email: [EMAIL PROTECTED]
Operating System: GNU/Linux
Open/Closed: Open
_______________________________________________________
Details:
Dear Sirs,
I am trying to use a Makefile to produce code for the Blackfin processor. My
development system uses Suse 10.1.
I have written a "Hello World" c program and a simple Makefile:
hello : hello.o
cc -o hello.c hello.o
hello.o : hello.c
cc -c hello.c
clean :
rm hello hello.o
The default 386 gcc compiler has the path: usr/bin/ and the Blackfin compiler
the path: /opt/uClinux/bfin-uclinux/bin/.
When I type "make", the 386 gcc compiler is always used.
I have tried adding: CC = bfin-uclinux-gcc as the first line of the Makefile,
also: override CC = bfin-uclinux-gcc. None worked.
The Blackfin compiler path is "visible" as:
bfin-uclinux-gcc -Wl,-elf2flt hello.c -o hello works.
I have experimented and checked the web with no success.
Can you please tell me how "make" can be forced to use the Blackfin compiler
rather than the 386 compiler?
Best wishes,
Peter
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?105544>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Savannah-help-public mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/savannah-hackers
