openpgm: bump to version release-5-2-122

At the same time perform a GitHub migration, since Google Code will
disappear soon.

- Bump to version release-5-2-122
- Switch to GitHub
- Remove trailing slash from OPENPGM_SUBDIR
- Remove unnecessary python dependencies
- Run the bootstrap.sh script it fails to autoreconf properly
- Add a hash file
- Rewrap the help text to 72 characters length
- Change the project URL

Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
---
 package/openpgm/Config.in    |   13 +++++++------
 package/openpgm/openpgm.hash |    2 ++
 package/openpgm/openpgm.mk   |   17 +++++++++++------
 3 files changed, 20 insertions(+), 12 deletions(-)
 create mode 100644 package/openpgm/openpgm.hash

On 10/21/2015 02:56 PM, Vicente Olivert Riera wrote:
[snip]
> - Run the bootstrap.sh script it fails to autoreconf properly
- Run the bootstrap.sh script; it fails to autoreconf properly

(missing semicolon to separate)
[snip]

Dear Vicente Olivert Riera,

On Wed, 21 Oct 2015 15:00:52 +0100, Vicente Olivert Riera wrote:
> On 10/21/2015 02:56 PM, Vicente Olivert Riera wrote:
> [snip]
> > - Run the bootstrap.sh script it fails to autoreconf properly
> - Run the bootstrap.sh script; it fails to autoreconf properly

I quickly looked at the bootstrap.sh script, and besides the messages in
Japanese (or what I guessed to be Japanese), nothing really unusual
stands out. What fails if you just have AUTORECONF = YES ?

Thomas

Dear Thomas Petazzoni,

On 10/21/2015 04:15 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
> 
> On Wed, 21 Oct 2015 15:00:52 +0100, Vicente Olivert Riera wrote:
>> On 10/21/2015 02:56 PM, Vicente Olivert Riera wrote:
>> [snip]
>>> - Run the bootstrap.sh script it fails to autoreconf properly
>> - Run the bootstrap.sh script; it fails to autoreconf properly
> 
> I quickly looked at the bootstrap.sh script, and besides the messages in
> Japanese (or what I guessed to be Japanese), nothing really unusual
> stands out. What fails if you just have AUTORECONF = YES ?

This is the failure:

>>> openpgm release-5-2-122 Configuring
>>> openpgm release-5-2-122 Autoreconfiguring
aclocal: error: couldn't open directory 'm4': No such file or directory
autoreconf: /br/output/host/usr/bin/aclocal failed with exit status: 1

With AUTORECONF = YES, we start running aclocal. I think it normally
starts running libtoolize, but since the m4 directory doesn't exist, it
starts directly with aclocal.

With the bootstrap script work because it will call libtoolize despite
of the m4 directory not existing.

If you prefer, this approach also works, although libtoolize is ran
twice (first by the hook, and then by autoreconf):

(I keep the line numbers to preserve the indentation)

13 OPENPGM_AUTORECONF = YES
14
15 # we need to run libtoolize before autoreconf, so the missing m4
16 # directory is created.
17 define OPENPGM_LIBTOOLIZE
18         cd $(@D)/$(OPENPGM_SUBDIR) && PATH=$(BR_PATH) libtoolize
19 endef
20 OPENPGM_PRE_CONFIGURE_HOOKS += OPENPGM_LIBTOOLIZE

Regards,

Vincent.

> 
> Thomas
>

Dear Vicente Olivert Riera,

On Wed, 21 Oct 2015 16:42:59 +0100, Vicente Olivert Riera wrote:

> 13 OPENPGM_AUTORECONF = YES
> 14
> 15 # we need to run libtoolize before autoreconf, so the missing m4
> 16 # directory is created.
> 17 define OPENPGM_LIBTOOLIZE
> 18         cd $(@D)/$(OPENPGM_SUBDIR) && PATH=$(BR_PATH) libtoolize
> 19 endef
> 20 OPENPGM_PRE_CONFIGURE_HOOKS += OPENPGM_LIBTOOLIZE

Why not just:

define OPENPGM_CREATE_M4_DIR
	mkdir -p $(@D)/$(OPENPGM_SUBDIR)/m4
endef
OPENPGM_POST_PATCH_HOOKS += OPENPGM_CREATE_M4_DIR

which works (tested locally).

Thanks,

Thomas