Thanks Isaac

I'll keep this mail so I can refer back to it and see what I can do.
Do you have a mail for Matteo and I'll chat with him about it?

Damien

On Mon, Dec 1, 2014 at 11:40 PM, Isaac Dunham <ibid.ag@???> wrote:
> On Mon, Dec 01, 2014 at 10:50:52PM +0000, Damien Hunter wrote:
>> Hello All,
>>
>> I'll cut straight to it, after a quick introduction. I'm a Developer
>> specializing in C, C++, Perl, Bash and Python. My OS of choice for
>> personal use is Mint, but I work with RHEL v6 and HP-UX 11, and not by
>> choice.
>>
>> I have never contributed to a Linux project of any kind, but I want
>> to. I've used OpenSuse Studio to put together a few packages, but
>> that's childs play, some thing a trained monkey could do. So I will be
>> putting together a few modules when I can and have been looking into
>> LFS as a guide.
>>
>> So the real question is, when and where do we begin? How will the work
>
> Matteo Panella just asked for someone who knows Perl to at least
> give an overview of how abi-dumper works; this is the current blocking
> issue.
>
> Quoting him:
>>> I'm trying to get an ABI dump of libudev/libgudev as built
>>> in the main Debian archive to ensure that the version built using eudev
>>> will be ABI-compatible with it.
>>>
>>> The reason is simple: avoid rebuilding every rdep of udev unless it's
>>> strictly necessary.
>
>>> Now for the nasty part: systemd's build system forces Link-Time
>>> Optimization on its ELF files, and this confuses abi-dumper to the point
>>> that it believes that eu-readelf found no symbol table nor DWARF
>>> sections (which isn't true, since everything is built with -g and the
>>> libraries have the proper .gnu_debuglink section header).
>>>
>>> This is where I need help from Perl wizards: abi-dumper is a big lump of
>>> Perl, and saying that I hate Perl is an understatement :-)
>>>
>>> I'm not asking to fix it for me (even though that would be appreciated
>>> *wink* *wink*), but I humbly ask for an high level overview of how it
>>> uses eu-readelf, vtable-dumper et al. to produce an ABI profile for the
>>> shared object, so I can try to understand what part of LTO is confusing it.
>>>
>>> You can use libudev.so.1.5.0 as your test case, just make sure to
>>> install systemd-dbg (otherwise it would rightfully complain that
>>> debugging symbols are missing).
>
>
>> be divided out? Will there be a Git, where we can fork and merge
>
> See https://github.com/devuan
>
> Hope this helps,
> Isaac Dunham