On 11/02/2015 12:41 PM, Gavin Smith wrote:
> On 2 November 2015 at 19:39, Dustin Laurence
> wrote:
>> First problem--configure dies, reporting that "C compiler cannot create
>> executables."
>
> Is there anything in config.log that could shed light on the causes of
> this failure?
Sorry, that
On 11/02/2015 12:42 PM, Gavin Smith wrote:
> But I should add that using CFLAGS is more usual:
> https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Compilers-and-Options.html#Compilers-and-Options
I tried adding just the architecture flags to CFLAGS, but it doesn't
really matter
On 11/02/2015 02:28 PM, Nick Bowler wrote:
> I strongly recommend against hardcoding all these program locations.
> If you put /opt/nfast/gcc/bin in your PATH, configure should pick them
> all up automatically based on the --host option.
The problem is that the final version is going to have comp
On 11/03/2015 11:58 AM, Dustin Laurence wrote:
> It says it can't find crt0.o
I did some more investigation on this, and one interesting thing is that
I can't find crt0.o either--it isn't anywhere in the SDK, though a
number of other *crt*.o files exist. That seems wrong since the
complaint is t
This may be premature to post, but I wanted to report that I did make it
past the crt0.o problem that had me tearing my hair out.
On 11/02/2015 12:42 PM, Gavin Smith wrote:
> But I should add that using CFLAGS is more usual:
> https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/
