| 1 |
On Thu, 2009-07-16 at 17:43 +0200, Fabian Groffen wrote: |
| 2 |
> Hi Markus, |
| 3 |
> |
| 4 |
> On 16-07-2009 17:02:03 +0200, Markus Duft wrote: |
| 5 |
> > i just (seemingly) finished preserve-libs support for x86-interix. |
| 6 |
> > attached is the svn diff against the modified tree, including the patch |
| 7 |
> > and the epatch... |
| 8 |
> > |
| 9 |
> > ok to commit, or do you want to integrate this into the prefix portage |
| 10 |
> > svn branch? |
| 11 |
> |
| 12 |
> It looks good to me, so I can commit it to the prefix branch. Just one |
| 13 |
> question (two actually): |
| 14 |
> - is it really a good idea to hardcode the path to objdump? (don't we |
| 15 |
> have symlinks to that stuff in our Prefix?) |
| 16 |
|
| 17 |
hm. the problem is the following: prefix has it's own objdump (binutils |
| 18 |
build fine...), but that one does not know about the "microsoft special |
| 19 |
hacks" about shared libraries (RPATH, SONAME, NEEDED), so exactly what |
| 20 |
i'm looking for. /opt/gcc.3.3/bin/objdump is present in all interix |
| 21 |
installations which install the GNU SDK (which is all installations that |
| 22 |
want to build software :)). |
| 23 |
|
| 24 |
Alternatively i could remove objdump from binutils, and link to |
| 25 |
the /opt/gcc.3.3/bin one, if that feels better. (i can't just use native |
| 26 |
binutils, because "ar" at least is somewhat unusable with c++). |
| 27 |
|
| 28 |
> - you mention PECOFF is actually more closer, but that winnt uses |
| 29 |
> different stuff but the same file; how is that going to work? does |
| 30 |
> Interix' objdump know something about .dll files or something? |
| 31 |
|
| 32 |
They share the basic file format ("container"), but have completely |
| 33 |
different contents. i'll have to do the same again (so a separate |
| 34 |
LinkageMapWinnt class), since objdump is not able to give usefull infos |
| 35 |
on .dll's... :( i will, for that purpose, have to write a small utility |
| 36 |
i can distribute with parity, which uses it's internal facilities to |
| 37 |
provide the required informations - thats not too much work, and parity |
| 38 |
has to be there anyway when building winnt binaries. |
| 39 |
|
| 40 |
Anything too hackish to make it into portage? ;) i guess it's the most |
| 41 |
clean way i can think of ATM... |
| 42 |
|
| 43 |
Cheers, Markus |
| 44 |
|
| 45 |
> |
| 46 |
> |
| 47 |
> |
Archives