elftoolchain-developers

[Elftoolchain-developers] Short-term roadmap

[Joseph K. <jk...@us...>]

Hi,

I would like to open discussion on our short term roadmap: i.e.,
planning for our first release.  The goal of this release would be
to produce a tarball that the other projects could start looking
at.

It seems to me that we have the following tasks need to be completed
before we can have any kind of release:

1) Bring libelf to the point where ar(1) can be implemented using
   it:
   1.1) libelf needs to be able to create ar(1) archives [Task #149800]
   1.2) libelf needs to handle BSD format ar(1) archives.  Currently
        it only understands SysV format archives. [Task #149801]

   These tasks would be owned by me, unless someone else wants to take
   them up.

2) Then we would need to retarget ar(1) to use the new libelf instead
   of libarchive. [Task #149994] (owned by jkoshy or kaiwang27)

3) Then a sanity-check porting pass to port ar(1) to other OSes.
 
`nm', `size' and `strings' run fine on NetBSD and FreeBSD.  I haven't
looked at `elfcopy' on NetBSD yet but do not anticipate trouble
either.

So the questions are:

- Do you think we should defer the first release till we have other
  tools ready?  If so, which tools would these be?

- If the idea of a release is ok, what OSes do we target for the first
  release?

Also: do you know of any organization offering a "build farm" with
different OSes?  I'd love to have a collection of buildbot/bitten
slaves that could build our source tree on different OSes
automatically.

Koshy

Re: [Elftoolchain-developers] Short-term roadmap

[Hyogeol L. <hyo...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Joseph Koshy :
| Hi,
|
| I would like to open discussion on our short term roadmap: i.e.,
| planning for our first release.  The goal of this release would be
| to produce a tarball that the other projects could start looking
| at.
|
| It seems to me that we have the following tasks need to be completed
| before we can have any kind of release:
|
| 1) Bring libelf to the point where ar(1) can be implemented using
|    it:
|    1.1) libelf needs to be able to create ar(1) archives [Task #149800]
|    1.2) libelf needs to handle BSD format ar(1) archives.  Currently
|         it only understands SysV format archives. [Task #149801]
|
|    These tasks would be owned by me, unless someone else wants to take
|    them up.
|
| 2) Then we would need to retarget ar(1) to use the new libelf instead
|    of libarchive. [Task #149994] (owned by jkoshy or kaiwang27)
|
| 3) Then a sanity-check porting pass to port ar(1) to other OSes.
|  
| `nm', `size' and `strings' run fine on NetBSD and FreeBSD.  I haven't
| looked at `elfcopy' on NetBSD yet but do not anticipate trouble
| either.
|
| So the questions are:
|
| - Do you think we should defer the first release till we have other
|   tools ready?  If so, which tools would these be?


Yes, 'brandelf'. It may does not take much time to implement/patch

'brandelf'. It is good idea to prepare 'as', but I'd like to put it 
later release

because it will take much time to implement.


|
| - If the idea of a release is ok, what OSes do we target for the first
|   release?

FreeBSD/NetBSD.
|
| Also: do you know of any organization offering a "build farm" with
| different OSes?  I'd love to have a collection of buildbot/bitten
| slaves that could build our source tree on different OSes
| automatically.
|
| Koshy


Best Regards,
Hyogeol Lee
- ----
hyo...@gm...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREKAAYFAkiFz4UACgkQ1D7/GiH6QSEduQCghMxxqEysj15k3ubON1froAsh
VLAAoMPCJkxl/1P0QkNpEr1F8skZdzsz
=XD9o
-----END PGP SIGNATURE-----

Re: [Elftoolchain-developers] Short-term roadmap

[Y G. A. N. <gir...@ap...>]

On 08/07/22 21:16 +0900, Hyogeol Lee said ...
> 
> Joseph Koshy :
> |
> | - If the idea of a release is ok, what OSes do we target for the first
> |   release?
> 
> FreeBSD/NetBSD.

Linux also, please :)

> | Also: do you know of any organization offering a "build farm" with
> | different OSes?  I'd love to have a collection of buildbot/bitten
> | slaves that could build our source tree on different OSes
> | automatically.

I came across openSUSE Build Service a few months ago, but I wasn't able
to sign in properly even once and the service is restricted to Linux.

Cheers,

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/

Re: [Elftoolchain-developers] Short-term roadmap

[Joseph K. <jk...@us...>]

> Yes, 'brandelf'. It may does not take much time to implement/patch
> 'brandelf'.

Agreed.

> It is good idea to prepare 'as', but I'd like to put it later
> release because it will take much time to implement.

Yes.  That's for the next release definitely.

Koshy

Re: [Elftoolchain-developers] Short-term roadmap

[Kai W. <kai...@gm...>]

This is a resend msg, I forgot to CC developer list last time.
Sorry about this.

On Mon, Jul 21, 2008 at 03:32:00AM -0000, Joseph Koshy wrote:
> 
> Hi,
> 
> I would like to open discussion on our short term roadmap: i.e.,
> planning for our first release.  The goal of this release would be
> to produce a tarball that the other projects could start looking
> at.

Great! :-)

> It seems to me that we have the following tasks need to be completed
> before we can have any kind of release:
> 
> 1) Bring libelf to the point where ar(1) can be implemented using
>    it:
>    1.1) libelf needs to be able to create ar(1) archives [Task #149800]
>    1.2) libelf needs to handle BSD format ar(1) archives.  Currently
>         it only understands SysV format archives. [Task #149801]
> 
>    These tasks would be owned by me, unless someone else wants to take
>    them up.

Just in case, I can help at least with 1.2) if need, and of course
I will help with testing.

> 2) Then we would need to retarget ar(1) to use the new libelf instead
>    of libarchive. [Task #149994] (owned by jkoshy or kaiwang27)

I'll take this task.

> 3) Then a sanity-check porting pass to port ar(1) to other OSes.
>  
> `nm', `size' and `strings' run fine on NetBSD and FreeBSD.  I haven't
> looked at `elfcopy' on NetBSD yet but do not anticipate trouble
> either.

elfcopy is not completed yet...

> So the questions are:
> 
> - Do you think we should defer the first release till we have other
>   tools ready?  If so, which tools would these be?

I think we should. elfcopy probably will not be finished at the time of
our first release, if the release is soon. (strip was basically finished though)
So I guess we should exclude elfcopy/strip from first release...

> - If the idea of a release is ok, what OSes do we target for the first
>   release?

NetBSD and FreeBSD? 

By the way, What does it looks like on OpenBSD? Is it easy to port
to Linux?

> Also: do you know of any organization offering a "build farm" with
> different OSes?  I'd love to have a collection of buildbot/bitten
> slaves that could build our source tree on different OSes
> automatically.
> 
> Koshy
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Elftoolchain-developers mailing list
> Elf...@li...
> https://lists.sourceforge.net/lists/listinfo/elftoolchain-developers