autoconf 2.64 and mb-gcc
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
autoconf 2.64 and mb-gcc
by Doug Geiger
::
Rate this Message:
Just wanted to give other folks a heads up about a regression in
autoconf 2.64 affected the configure script for usrp2-firmware. Basically the compiler test now includes stdio.h and fopen in the test program (instead of a simple empty main function). This breaks with my install of mb-gcc. I imagine there are other work-arounds, but I found this one on the autoconf mailing list (http://lists.gnu.org/archive/html/autoconf/2009-09/msg00114.html). Note the work-around has potential side-effects, but I was able to build the firmware without issues. Apparently this regression in autoconf is being addressed upstream. FYI - Ubuntu 9.10 ships with autoconf 2.64, which is how I got bit by this one. Doug -- Douglas Geiger Code 5545 U.S. Naval Research Laboratory Washington, DC 20375 (202) 767-9048 douglas.geiger@... _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@... http://lists.gnu.org/mailman/listinfo/discuss-gnuradio |
|
|
autoconf 2.64 & warnings during bootstrap
by Michael Dickens-3
::
Rate this Message:
Speaking of autoconf 2.64 .. I'm using it on Mac OS X (via MacPorts),
and it generally works. During bootstrap, it prints out the following 4 times: configure.ac:127: warning: AC_REQUIRE: `AC_PROG_F77' was expanded before it was required ../../lib/autoconf/fortran.m4:272: AC_LANG_COMPILER(Fortran 77) is expanded from... ../../lib/autoconf/lang.m4:315: AC_LANG_COMPILER_REQUIRE is expanded from... ../../lib/autoconf/general.m4:2665: AC_LINK_IFELSE is expanded from... config/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... config/libtool.m4:4158: _LT_LINKER_SHLIBS is expanded from... config/libtool.m4:6583: _LT_LANG_F77_CONFIG is expanded from... config/libtool.m4:785: _LT_LANG is expanded from... config/libtool.m4:768: LT_LANG is expanded from... config/gr_fortran.m4:20: GR_FORTRAN is expanded from... configure.ac:127: the top level but otherwise these warnings don't seem to affect how configure performs. It's always nice to have a clean(er) output for bootstrap, but I can live with this (for now). - MLD _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@... http://lists.gnu.org/mailman/listinfo/discuss-gnuradio |
|
|
Re: autoconf 2.64 and mb-gcc
by Josh Blum-2
::
Rate this Message:
I am using the mb-gcc from xilinx EDK and the configure breaks for me as well on ubuntu 9.10. Here is the breakdown in config.log
configure:3078: mb-gcc -O2 conftest.c >&5 /opt/microblaze/lin/bin/../lib/gcc/microblaze-xilinx-elf/4.1.1/../../../../microblaze-xilinx-elf/lib/libxil.a(write.o): In function `write': /proj/fv1/gnu_builds/head/mb/build/lin/bld_gcc/gcc/libgloss/microblaze/write.c:36: undefined reference to `outbyte' /proj/fv1/gnu_builds/head/mb/build/lin/bld_gcc/gcc/libgloss/microblaze/write.c:34: undefined reference to `outbyte' /opt/microblaze/lin/bin/../lib/gcc/microblaze-xilinx-elf/4.1.1/../../../../microblaze-xilinx-elf/lib/libxil.a(read.o): In function `read': /proj/fv1/gnu_builds/head/mb/build/lin/bld_gcc/gcc/libgloss/microblaze/read.c:35: undefined reference to `inbyte' collect2: ld returned 1 exit status configure:3082: $? = 1 configure:3119: result: configure: failed program was: This is all probably related to stdio not being setup for the microblaze. Anyway, to get the configure to pass, I can compile the test program with void inbyte(){} and void outbyte(){} defined, and it works. So, we just need to setup autoconf to define these dummy functions at configure time, or to link against something with said functions. Which I am trying to figure out now... -Josh
On Tue, Nov 3, 2009 at 11:03 AM, Doug Geiger <douglas.geiger@...> wrote: Just wanted to give other folks a heads up about a regression in autoconf 2.64 affected the configure script for usrp2-firmware. Basically the compiler test now includes stdio.h and fopen in the test program (instead of a simple empty main function). This breaks with my install of mb-gcc. I imagine there are other work-arounds, but I found this one on the autoconf mailing list (http://lists.gnu.org/archive/html/autoconf/2009-09/msg00114.html). Note the work-around has potential side-effects, but I was able to build the firmware without issues. Apparently this regression in autoconf is being addressed upstream. _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@... http://lists.gnu.org/mailman/listinfo/discuss-gnuradio |
| Free embeddable forum powered by Nabble | Forum Help |
