Re: [gentoo-alt] interix preserve-libs

[Fabian Groffen]

On 22-07-2009 10:10:32 +0200, Markus Duft wrote:
> > ah.  Well, I meant to look at the patch in detail last night, commit it
> > and make a new snapshot ... but something came inbetween.
>
> ah, well - no problem :)
>
> >
> > I have to look into detail, because it seems your PECOFF actually has
> > exactly the same behaviour as ELF, so I'd like to see if we can make the
> > LinkageMapPeCoff a shallow wrapper around the LinkageMap(ELF) one, to
> > avoid duplication.  Also, I'm not sure if scanpecoff should be in
> > Portage, or in a bumped version of pax-utils.
>
> Hm. The LinkageMapPeCoff inherits from LinkageMap, and thus already has
> as low code duplication as possible. i _have_ to implement the parsing
> (if you can call simple reading from stdout "parsing" ;)) in a separate
> "rebuild" method, and i _have_ to implement the _ObjectKey myself, since
> inodes are no good on windows...

Ah, ok, then it should already be optimal.

> scanpecoff's location... hmmm... there is no "really good" place for it.
> since it handles both interix and winnt, it is not suited to be put into
> parity, nor into binutils or something thelike. i think portage is the
> best place, since only portage will ever use it (i hope so - nobody else
> will have fun with it, since it only produces _exactly_ the format
> required by portage...). However, i'm open to location suggestions :)

I think the following will get us up to speed quickly:
- rename the current script to "readpecoff" or something
- ship it with portage for the time being

Then I'd like it when we could get a scanpecoff (like scanmacho and
scanelf, the C-programs from pax-utils) that does the job, replacing
your huge bash-script.

> > At the moment I'm trying to open a docx file from Microsoft that should
> > be the specification of PECOFF.
>
> uh... you won't have fun with that document - i know it by rote ;) it
> does _not_ specify how both interix and winnt handle runpaths, needed
> shared libs, etc.

I can't even open it.  OpenOffice die hard aborts on it (Signal 6).

> how interix handles those things is completely hidden somewhere in the
> interix loader/binary format/binutils patches at M$. (However the
> current binutils 2.17 patches are open, so i could have a look at it -
> the patch is about 300.000 lines long ;*( ...)

I once split that patch into our binutils ebuild for 2.17, maybe it's
useful?

> The format used by winnt to model shared library features (rpath,
> needed, etc.) is defined by parity (native win32 does not support those
> out of the box...) - it builds upon the PE/COFF specs, but of course it
> does it's own things :) if you want to know what it does exactly -> ask
> me, as i wrote it ;)


-- 
Fabian Groffen
Gentoo on a different level