discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] autoconf 2.64 and mb-gcc


From: Josh Blum
Subject: Re: [Discuss-gnuradio] autoconf 2.64 and mb-gcc
Date: Sun, 8 Nov 2009 01:19:18 -0800

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 <address@hidden> 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.
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
address@hidden



_______________________________________________
Discuss-gnuradio mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


reply via email to

[Prev in Thread] Current Thread [Next in Thread]