1 |
On Wed, 2009-07-22 at 10:54 +0200, Fabian Groffen wrote: |
2 |
> On 22-07-2009 10:31:42 +0200, Markus Duft wrote: |
3 |
> > On Wed, 2009-07-22 at 10:22 +0200, Fabian Groffen wrote: |
4 |
> > > On 22-07-2009 10:10:32 +0200, Markus Duft wrote: |
5 |
> > [snip] |
6 |
> > > |
7 |
> > > I think the following will get us up to speed quickly: |
8 |
> > > - rename the current script to "readpecoff" or something |
9 |
> > > - ship it with portage for the time being |
10 |
> > |
11 |
> > ok. i updated the patch -> attached. |
12 |
> |
13 |
> Good, will you apply it to the ebuild? I'll do my best to apply it |
14 |
> tonight to portage. |
15 |
|
16 |
repoman commit done. |
17 |
|
18 |
> |
19 |
> > > Then I'd like it when we could get a scanpecoff (like scanmacho and |
20 |
> > > scanelf, the C-programs from pax-utils) that does the job, replacing |
21 |
> > > your huge bash-script. |
22 |
> > |
23 |
> > puh. i could try to implement such a thing, but to be correct i would |
24 |
> > need one for interix, and one for windows - that the "readpecoff" script |
25 |
> > can handle both is more a hack than a solution ;) |
26 |
> > |
27 |
> > OTOH - why not..? it feels like a good idea to have such a utility. it |
28 |
> > could detect wether the file is interix/winnt and handle it correctly - |
29 |
> > maybe i could also lookup the interix shared library section format from |
30 |
> > the binutils patch, and implement it there - so that scanpecoff is |
31 |
> > faster than parsing objdump output all the time... |
32 |
> |
33 |
> That's the idea, and also such that we can inspect interix/windwows |
34 |
> files from Solaris, Darwin, Linux, etc. |
35 |
|
36 |
hm, i see. that will be some extra effort, since i need some parts of |
37 |
parity to be able to parse all this, and parity only builds on |
38 |
windows/interix right now. however the parts i need are portable - so |
39 |
maybe i need to split into two separate packages... we'll see. |
40 |
|
41 |
Cheers, Markus |
42 |
|
43 |
> |
44 |
[snip] |