[Efi332] Building newlib/libgloss for MPC555

[David Eicher]

Well, I ran the install, it installed in my compiler directory
(powerpc-elf), so I moved the lib and include directories to
usr/local/lib/powerpc-elf/lib and usr/local/lib/powerpc-elf/include. It's
amazing I've got this far, thanks much for all the help. 

The bad news..., I have libraries in the lib directory, but also a
subdirectory called "le" has libraries in it, as well as "nof" and "nof/le"
and "nof/und" and "und". So, there are about six libc, six libm, etc.

Does anyone know what these directories are for? Which copy of the libraries
should I point my linker to when I build target code?

I need to modify my libgloss too, and am looking for documentation/input on
how to build that library.

Thanks much for any insight you might be able to offer.

Dave




-----Original Message-----
From: efi332-bounces at diy-efi.org [mailto:efi332-bounces at diy-efi.org] On
Behalf Of Gunter Magin
Sent: Tuesday, July 26, 2005 5:10 AM
To: efi332 at diy-efi.org
Subject: Re: [Efi332] Building newlib/libgloss for MPC555

On Tue, Jul 26, 2005 at 04:27:36AM -0700, David Eicher wrote:
> Hello,
> 
> I started make before going to bed, I don't know how long it ran, but it
was
> quite a while. Under the directory I created I now have:

<...>
Looks good. Congrats.

Don't forget to run a "make install" in the toplevel newlib work
directory, (the one in which you called ../newlib-x.x.x/configure). This
run transfers the relevant end results of your nightly compile run into
the installation directory. Otherwise, your target app Makefile will
not find the libs and include files. You have specified the install path
with the --prefix option (or left the default /usr/local), and that is
merged into the Makefiles in the work tree.

After that, you are free to cleanup (purge) the build tree, and recover
some MB disk space, for example run a "make clean". But wait, you still
have to add libgloss support for your particular target board....

> Under each of these subdirectories there are tons of files and libraries.
I
> am now looking for documentation that explains which of these sets of
> directories I'm suppose to work with to get me a lib or two I can link in
> with my target code. There are almost countless numbers of libraries here,
> how does one choose?

Now you know why your Makefile is that long: it contains these
informations.

gm
_______________________________________________
Efi332 mailing list
Efi332 at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/efi332