[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[microblaze-uclinux] Gcc build bug?
I get the following error building on windows using the EDK microblaze
tools, but linking with the libraries from the John's toolchain build:
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
Is this a problem with the gcc libs, or am I somehow getting references
the the EDK built libraries in my code? John, does that path look like
its from your build?
I included the transcript below.
--Scott
> -----OrC:\\Impulse\\CoDeveloper\\/uClinux/elf2flt/ld-elf2flt -v -Os -g
-elf2flt -LC:\\Impulse\\CoDeveloper\\/uClinux/lib/uClibc/lib -o mand
mand_sw.o co_init.o libimpulsec.a
C:\\Impulse\\CoDeveloper\\/uClinux/lib/uClibc/lib/crt0.o -lc
C:\\Impulse\\CoDeveloper\\/uClinux/tools/lib/gcc-lib/microblaze/2.95.3-4
/libgcc.a
C:\\Impulse\\CoDeveloper\\/uClinux/tools/microblaze/lib/libc_hard_shift.
a -lc
+ ARG1= -v -Os -g -LC:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib
mand_sw.o co_init.o libimpulsec.a
C:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib/crt0.o -lc
C:\Impulse\CoDeveloper\/uClinux/tools/lib/gcc-lib/microblaze/2.95.3-4/li
bgcc.a
C:\Impulse\CoDeveloper\/uClinux/tools/microblaze/lib/libc_hard_shift.a
-lc
+ C:\Impulse\CoDeveloper\/uClinux/elf2flt/mktemp /tmp/flt-XXXXXX
+ NEWLDSCRIPT=/tmp/flt-a04076
+ SEDOP= -e s/^R_RODAT// -e /^W_RODAT/d
+ [ ]
+ [ ]
+ [ -z ]
+ LDSCRIPT=C:\Impulse\CoDeveloper\/uClinux/elf2flt/../lib/elf2flt.ld
+ [ -f C:\Impulse\CoDeveloper\/uClinux/elf2flt/../lib/elf2flt.ld ]
+ sed -e s/^R_RODAT// -e /^W_RODAT/d
+ LDSCRIPT=/tmp/flt-a04076
+ [ yes = no ]
+ mb-ld -r -d -o mand.elf2flt -v -Os -g
-LC:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib mand_sw.o co_init.o
libimpulsec.a C:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib/crt0.o -lc
C:\Impulse\CoDeveloper\/uClinux/tools/lib/gcc-lib/microblaze/2.95.3-4/li
bgcc.a
C:\Impulse\CoDeveloper\/uClinux/tools/microblaze/lib/libc_hard_shift.a
-lc
GNU ld version 2.10.1 Xilinx EDK 6.3 Build EDK_Gmm.10 (with BFD 2.10.1)
+ mb-ld -LC:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib -T
/tmp/flt-a04076 -Ur -o mand.elf mand.elf2flt
+ mb-ld -LC:\Impulse\CoDeveloper\/uClinux/lib/uClibc/lib -T
/tmp/flt-a04076 -o mand.gdb mand.elf2flt
mand.elf2flt: In function `__subdf3':
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld/libgloss/mic
roblaze/floatlib/subdf3.c:70: undefined reference to `outbyte'
mand.elf2flt:/home/sid/builds/EDK_Gm/env/Jobs/MDT/sw/lin/gnu1/newlib_bld
/libgloss/microblaze/floatlib/subdf3.c:70: more undefined references to
`outbyte' follow
+ exit 1
make: *** [mand] Error 1
iginal Message-----
> From: owner-microblaze-uclinux@itee.uq.edu.au
> [mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of
> John Williams
> Sent: Sunday, October 31, 2004 9:22 PM
> To: microblaze-uclinux@itee.uq.edu.au
> Subject: [microblaze-uclinux] uClinux support for FSL devices
>
>
> Hi folks,
>
> I'm releasing some of my research drivers into the public
> CVS. I think
> (hope?) that it's interesting work, and may be useful in broadening
> awareness of what Microblaze uClinux can do.
>
> On a more philsophical level, I think that the best validation of
> research is for it to find use in the wider community. If
> this proves
> useful to someone, I'd love to hear about it.
>
> First cab off the rank is a generic FSL FIFO driver. FSL is
> one of the
> bus architectures supported by Microblaze, that provides
> register mapped
> streaming IO. An FSL bus is essentially a hardware FIFO, with simple
> handshaking signals. Interfacing to FSL is so easy it's
> almost trivial,
> particularly if you have an example to follow. Read all
> about it in the
> Microblaze HW reference.
>
> This driver create a linux device abstraction over the top of an FSL
> channel, providing software buffering and read/write/ioctl
> operations.
> If you have an FSL-enabled core, you can simply cat (or
> write() ) data
> to the device node, and it is automagically buffered and
> streamed to the
> FSL channel. IOCTL calls are used to reset the buffers,
> send and read
> control words, that sort of thing. I chose the misc device
> major number
> (10), with minor numbers 192-199. If this is a horrible
> clash with some
> existing device let me know and we'll pick a different number.
>
> The driver lives in linux-2.4.x/drivers/misc/fslfifo - and is
> available
> in CVS right now.
>
> Regards,
>
> John
>
> PS If you are writing your own FSL-enabled device drivers or
> user code,
> but don't need this driver, then you may still find the file
> /include/asm-microblaze/fsl.h useful. It's a bunch of support macros
> for getting and putting to/from FSL channels, and interpreting the
> status results and so on.
>
> PPS For those who know about FSL - my personal policy in
> uClinux is that
> blocking FSL ops are strictly verboten... Nothing locks microblaze
> harder than a blocking get on a non-existent FSL port! Not
> even an NMI
> will save you - it's reset-city...
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/