On 2 November 2015 at 19:39, Dustin Laurence <dllaurence@xxxxxxxxxxxxxx> 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? It might be simpler to debug by getting the configure run right from the command line first, instead of doing it from a Makefile. In fact, running configure from a Makefile you wrote yourself is unusual. > Second Problem: I don't know The Right Way to pass in the architecture > flags to autoconf (-march, text segment address, etc.). I tried > overriding CFLAGS with the values I use for my own code, but that didn't > work. Plus, I suspect that I shouldn't simply set CFLAGS anyway, since > the library build system presumably has some important opinions about > that. I guess I simply want to add my architecture flags to the > library's choices, not override. I tried appending them to the value of > CC, but that failed as well. I imagine I'm missing some basic autoconf > knowledge here. These generic installation instructions: https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Multiple-Architectures.html show putting flags directly in CC. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
