Re: [microblaze-uclinux] toolchain build instructions

[John Williams <jwilliams@itee.uq.edu.au>]

WARNING: This e-mail has been altered by ITEE at UQ's anti-virus
filter MIMEDefang.  Following this paragraph are indications of 
the actual changes made.  For more information about ITEE at UQ's
anti-virus policy, please contact postmaster@itee.uq.edu.au. 

Bad filename 'buildit.sh'

The attachment 'buildit.sh' was removed from this email as it
violated ITEE's anti-virus policy.  If you require this document,
please contact the sender and arrange an alternate means of
receiving it (ask them to zip it up or change the extension,
for instance).

Hi Brett,

I've had some success with the toolchain build process, but it's not 
without errors or mysteries.  Attached is a script called buildit.sh, 
that basically encapsulates the instructions I posted to you via the 
Xilinx forum a few weeks ago.

For some reason (that I have not yet fully determined), you only seem to 
get "one go" at building gcc.  This is evidenced by the necessary step 
of touching the gcc/gcc/configure file before running make.  I can't 
explain it, and am not very satisfied with it, but there you go. 
Perhaps you will have some luck decyphering it.

Anyway, create a place to do the new build, and unzip the source 
distribution into it.  Setup the relative directories at the top of the 
buildit.sh script - it should be pretty self-explanatory.

Then, run the script, and see how it goes.  On my setup, it fails part 
way through the final 'make install' of gcc, but by then the binaries 
have been built and I can copy them out and use them etc.  I haven't 
checked re: building the libraries, I've already got copies of those and 
haven't tried rebuilding them.  Didn't test it thoroughly but a trivial 
(ie null) main() function compiled without errors.

Strangeness occurs if I re-run the script without first completely 
deleting the source directories and unzipping a fresh copy.  Obviously 
something to do with the configuration process and some files left 
behind, but that's as far as I got.  I'm no gcc toolchain expert, maybe 
you can find someone who is and straighten this mess out.

Please let me know how you go with it so we can get it properly working 
and documented.

Cheers,

John



John Williams wrote:

> Brett Boren wrote:
> 
>> Hello, while I'm not specifically interested in uclinux for the
>> microblaze, I am interested in finding out who posted the linux compiled
>> toolchain. I need to modify the code generator for my thesis and since I
>> can't even get the vanilla version to build there's no hope of getting a
>> modified version working. Any help will be most appreciated. 
> 
> 
> Hi Brett,
> 
> I've contacted the original contributor of the binaries to see if they 
> can remember and decribe the process to rebuild mb-gcc under linux. It's 
> something I'd like to know about as well, so we can always track the 
> latest compiler version.  I'll let you know what I discover.
> 
> Regards,
> 
> John
> 
> 
> ___________________________
> 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/