[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] C++ output problems
> Hmm, so building C++ programs for mb-uclinux? Although I have to
> wonder, if they make no output, how you know they work? A philosophical
> question perhaps? :)
Well.. they compile and execute silently, with no error messages. To move this out of the realms of faith, I guess I could try putting one into an infinite loop and watching top.
> Those complaints about the toolchain are ancient - these days building
> mb-gcc and friensd is a lot easier (under a Linux box at least - haven't
> tried lately under Windows). I have a script that I wrote that does
> most of it automagically, I'll dig it out and send it to the list.
That sounds very useful, I'll be waiting for it. I have about two weeks left in the research position I'm working on so there may just be enough time to fix a few things.
> Grab a copy of the gnu sources from the xilinx website and you should be
> right to go.
> My feeling is that there's not much if anything you'll need to do in the
> compiler, so much as getting STL port and all of the build environmetn
> stuff in uClinux-dist working for Microblaze. Also there's the init and
> fini preamble/postamble support in the uClibc runtime libraries as well.
It wasn't the compiler as much as the custom libc.a and gcclib.a in the microblaze-elf-tools directory that I wanted to work with, as that is where the current conflicts appear to reside,
and I'm guessing somewhere in there is where I need to define inbyte and outbyte. Anyways, being able to with with the libraries and get simple C style output working will be a first
step towards larger STL implementations.
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/