g21k and archiver

[Alessandro Basili]

Hi,
I'm trying to revive the g21k cross-compiler based on gcc that Analog
Devices released under a GPL license back in the 90s (see
http://code.google.com/p/g21k/)
I'm compiling it with gcc-4.4.1 and at the beginning I had several
problems during compilation, including an increased number of
shift/reduce error from bison.
I think I got most of the problems out of the way now and after
compiling the runtime C library also from AD I'm now having a small
problem with the archiver ar.

When I compile with the following:

> g21k -o foo foo.asm -a 21kc.ach -g -O -Wall -mADSP21020 -m -L/usr/local

I get the following linker errors:

> %ld21000 - Linker Error
>
> Archive symbol directory is missing from archive /usr/local/21k/lib/libc.a
>
>
>
> %ld21000 - Linker Error
>
> Archive symbol directory in archive /usr/local/21k/lib/libc.a is too large
>
>
> %ld21000 - Linker Error
>
> Can't read archive symbol directory of archive /usr/local/21k/lib/libc.a
>

The linker apparently expects a "symbol directory", but then reports the
"symbol directory ... is too large".

Is it possible the port that was done at that time was considering a
different format of the archive? It seems to me there is some kind of
incompatibility which is preventing the linker to use the objects in the
archive.

On top of it nm does not recognize the file format of the objects in the
archive (but maybe this is expected since the cross-compiler will
produce an object suited for a specific architecture).

Unfortunately neither the author of the port, nor the current maintainer
is answering.


--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Alessandro Basili]

On 11/15/2011 9:40 AM, Alessandro Basili wrote:
> Hi,
> I'm trying to revive the g21k cross-compiler based on gcc that Analog
> Devices released under a GPL license back in the 90s (see
> http://code.google.com/p/g21k/)

> [...]

> The linker apparently expects a "symbol directory", but then reports the
> "symbol directory ... is too large".
>

I have found that the object files produced by the cross-compiler are of
type "COFF DSP21K" and if I want to archive them apparently ar does not
create an archive symbol directory.

Now my question would be, is there any tool/application/trick to archive
these objects in order to create a library?

Does anyone in the community know why the application /file/ does
recognize the format, while /ar/ and /nm/ others do not?

p.s.: I am posting similar threads on comp.dsp in the hope that someone
has already worked with this cross-compiler.