Skip to contentSkip to conversation

Activating autotools updates

DISCUSSION Koen Kooi 6 participants 13 messages Jul 25, 2007 – Aug 6, 2007

lore
Share & tools
lore

Koen Kooi

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig-native 0.22 and m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people to try to build their favourite target and report back.

regards,

Koen

(you can test it by commenting the 'DEFAULT_PREFERENCE = -1' in the recipes) -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGpxHbMkyGM64RGpERAoRRAJ96hmirIkqd5v1frEmetok80YIKdgCghuC0 2ZdyjeESMdlKMvnLqfbLWUM=
=hJYl
-----END PGP SIGNATURE-----

#1 lore raw

Am 25.07.2007 um 11:03 schrieb Koen Kooi:

Quoted 8 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig-native 0.22 and m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people to try to build their favourite target and report back.

Hi Koen,

I would propose to use ipkg-diff. Do a old build, do a new build and compare the resulting packages using ipkg-diff which is in oe contrib.

z.

author
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Holger Freyther schreef:

Quoted 13 lines

Am 25.07.2007 um 11:03 schrieb Koen Kooi:

Quoted 10 lines

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig- native 0.22 and
m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people
to try to build their favourite target and report back.

Quoted 4 lines

Hi Koen,

I would propose to use ipkg-diff. Do a old build, do a new build and compare the resulting packages using ipkg-diff which is in oe contrib.

That would be inconclusive, since a difference might be a good thing. I'm interesting in people running the generated packages.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGpxsDMkyGM64RGpERAqXWAJ4vtKMyEPjUkMyu8v05TYTywuAV5ACfZecw w22KlXyXrvzpfhYFZn3HJxg=
=EhQl
-----END PGP SIGNATURE-----

author
#3 lore raw
In reply to Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:

Quoted 5 lines

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig-native 0.22 and m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people to try to build their favourite target and report back.

After multiple success reports I'd like to propose the following timeline:

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default
20070816: make pkgconfig-native 0.22 the default
20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

what do you think?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGqJWhMkyGM64RGpERAvBcAJ0YKMzrl8ASaDjhA6xzAN+JxS9X/gCeL8GI 7n/RcjqzkspmMk/RWkel9q0=
=B3QE
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 7 lines · Koen Kooi

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default
20070816: make pkgconfig-native 0.22 the default
20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

what do you think?

+3.141592654 from me.

Graeme

#5 lore raw
In reply to Koen Kooi
Quoted 5 lines · Koen Kooi

After multiple success reports I'd like to propose the following timeline:

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default

make automake 1.9.6 or 1.10 the default

Quoted 3 lines

20070816: make pkgconfig-native 0.22 the default 20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

Who will do each test?

Signature · 5 lines
JID: hrw-jabber.org
OpenEmbedded developer/consultant

        "To be or not to be that is the question.":
         every programmer knows the answer $2b or (not $2b) is $ff.
author
#6 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcin Juszkiewicz schreef:

Quoted 9 lines
Quoted 5 lines · Koen Kooi

After multiple success reports I'd like to propose the following timeline:

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default

make automake 1.9.6 or 1.10 the default

I haven't tested that, has anyone done builds from scratch with that?

Quoted 5 lines
Quoted 3 lines

20070816: make pkgconfig-native 0.22 the default 20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

Who will do each test?

I'd guess the person that encounters such a hack. IOW "I have no idea".

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGqJhpMkyGM64RGpERAjHNAJ9NpE9/OwI6elauyGB/RRKTgDJPBACgkOzW n6wN2AzyCbxH9O/SoGCs2l8=
=LLHF
-----END PGP SIGNATURE-----

author
#7 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:

Quoted 10 lines

Marcin Juszkiewicz schreef:

Quoted 7 lines

Dnia czwartek, 26 lipca 2007, Koen Kooi napisaB:

Quoted 4 lines

After multiple success reports I'd like to propose the following timeline:
20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default

make automake 1.9.6 or 1.10 the default

I haven't tested that, has anyone done builds from scratch with that?

I brief test showed breakage, so automake 1.10 proponents have some work to do before asking it to be activated :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGqa0RMkyGM64RGpERAk32AKCQAbVqg/QWf4zEy7HAHIzeZhGHwgCgvQhX WOvufiuPWa0VDYC6ZmzbkRM=
=CcZn
-----END PGP SIGNATURE-----

#8 lore raw
In reply to Koen Kooi

Hello Koen,

Quoted 10 lines · you

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:

Quoted 5 lines

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig-native 0.22 and m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people to try to build their favourite target and report back.

Quoted 6 lines

After multiple success reports I'd like to propose the following timeline:

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default
20070816: make pkgconfig-native 0.22 the default
20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

Don't forget automake 1.10.

Quoted 5 lines

what do you think?

regards,

Koen

[]

Signature · 2 lines
Best regards,
 Paul                            mailto:[email protected]
#9 lore raw
In reply to Koen Kooi
Quoted 10 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:

Quoted 5 lines

Hi,

At guadec we discussed activating autoconf-native 2.61, pkgconfig-native 0.22 and m4-native 1.4.8. The test builds we did didn't show any errors but we'd like more people to try to build their favourite target and report back.

Quoted 8 lines

After multiple success reports I'd like to propose the following timeline:

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default
20070816: make pkgconfig-native 0.22 the default
20070816+: remove autotools hacks in recipes (e.g overriding do_configure)

what do you think?

Sounds good, +1 from me.

Regards,

:M:

Signature · 1 line
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
#10 lore raw
In reply to Koen Kooi
Quoted 4 lines · Koen Kooi

After multiple success reports I'd like to propose the following timeline:

20070816: make pkgconfig-native 0.22 the default

===========================================================
Revision: c575740a3b6935cc9e85bcc4e6f3cec52b4c4028
Ancestor: 12b138279c360841bb21419b7866a60b4a10932c
Author: [email protected]
Date: 2007-08-05T12:28:40
Branch: org.openembedded.dev

Added files:
packages/pkgconfig/pkgconfig.inc
Modified files:

         packages/pkgconfig/pkgconfig-native_0.22.bb
         packages/pkgconfig/pkgconfig_0.15.0.bb
         packages/pkgconfig/pkgconfig_0.22.bb

ChangeLog:

pkgconfig: sync with poky
===========================================================

This changeset enabled pkg-config 0.22 in OE as this removed DEFAULT_PREFERENCE = "-1" from recipe. Anyway it should work - in Poky we (OpenedHand) use it since Poky Linux 3.0 'blinky' was released.

Signature · 5 lines
JID: hrw-jabber.org
OpenEmbedded developer/consultant

  Any smoothly functioning technology will have the appearance of magic.
  		-- Arthur C. Clarke
author
#11 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcin Juszkiewicz schreef:

Quoted 20 lines
Quoted 4 lines · Koen Kooi

After multiple success reports I'd like to propose the following timeline:

20070816: make pkgconfig-native 0.22 the default

===========================================================
Revision: c575740a3b6935cc9e85bcc4e6f3cec52b4c4028
Ancestor: 12b138279c360841bb21419b7866a60b4a10932c
Author: [email protected]
Date: 2007-08-05T12:28:40
Branch: org.openembedded.dev

Added files:
packages/pkgconfig/pkgconfig.inc
Modified files:

         packages/pkgconfig/pkgconfig-native_0.22.bb
         packages/pkgconfig/pkgconfig_0.15.0.bb
         packages/pkgconfig/pkgconfig_0.22.bb
Quoted 7 lines

ChangeLog:

pkgconfig: sync with poky
===========================================================

This changeset enabled pkg-config 0.22 in OE as this removed DEFAULT_PREFERENCE = "-1" from recipe.

Oops, that has been fixed now.

Quoted 2 lines

Anyway it should work - in Poky we
(OpenedHand) use it since Poky Linux 3.0 'blinky' was released.

I know it works, otherwise I wouldn't have proposed it, but I'd like to stick to my own timeline :)

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGtvWkMkyGM64RGpERAhzxAJ0dE5rvVkmKgo36LRpHhAwpZpa20wCgrS9e /EyKRz9GjBvIxEVgb7nnbHE=
=agGv
-----END PGP SIGNATURE-----

#12 lore raw
In reply to Koen Kooi
Quoted 3 lines · Koen Kooi

20070802: make m4-native 1.4.8 the default
20070809: make autoconf-native 2.61 the default
20070816: make pkgconfig-native 0.22 the default

In Poky we (OpenedHand) upgraded to autoconf 2.61, m4 1.4.8, pkgconfig 0.22 and automake 1.9.6 (after Poky Linux 3.0 'blinky' release) and it produce working images.

Signature · 4 lines
JID: hrw-jabber.org
OpenEmbedded developer/consultant

       I'm broken. Please show this to someone who can fix me [TeX]