Bug 1603 - Add recipe supporting autoconf-nativesdk and automake-nativesdk
Summary: Add recipe supporting autoconf-nativesdk and automake-nativesdk
Status: VERIFIED FIXED
Alias: None
Product: ADT
Classification: Yocto Project Subprojects
Component: kernel analysis (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Low enhancement
Target Milestone: 1.2 M1
Assignee: Wenzong.Fan
QA Contact:
URL:
Whiteboard: (P2) (QA testing completed) Done
Depends on:
Blocks: 1909
  Show dependency tree
 
Reported: 2011-10-04 10:44 UTC by Jessica
Modified: 2012-01-17 20:54 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2011-10-04 10:44:23 UTC
The new libtool m4 macros(supporting --with-libtool-sysroot) resides in the directory where host aclocal can not find it by default. This requires the user to manually add that directory using -I options. Adding automake(autoconf)-nativesdk into meta-toolchain would help this.
Comment 1 Lianhao Lu 2011-11-07 21:43:17 UTC
Per Kai Kang's request, I put the procedure of how to verify this bug is closed:

1. Make sure automake-nativesdk and autotool-nativesdk can be built.
2. Make sure automake-nativesdk and autotool-nativesdk is included in meta-toolchain.
3. Using the meta-toolchain mentioned in step 2, try to build an autotool project with:
 ./aclocal
 ./autoheader
 ./autoconf
 ./automake
 ./configure --host=<your target host triplet> --with-libtool-sysroot=<your sysroot dir>

and make sure the ./configure doesn't complain about the unknown parameter of --with-libtool-sysroot=.
Comment 2 Kai Kang 2011-11-16 19:26:15 UTC
(In reply to comment #1)
> Per Kai Kang's request, I put the procedure of how to verify this bug is
> closed:
> 
> 1. Make sure automake-nativesdk and autotool-nativesdk can be built.
                                      ~~~~~~~~ do you mean autoconf?
Comment 3 Lianhao Lu 2011-11-17 07:08:47 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Per Kai Kang's request, I put the procedure of how to verify this bug is
> > closed:
> > 
> > 1. Make sure automake-nativesdk and autotool-nativesdk can be built.
>                                       ~~~~~~~~ do you mean autoconf?

Yes. It should be autoconf-nativesdk. Sorry for my typo.
Comment 4 Kai Kang 2011-11-20 18:30:34 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Per Kai Kang's request, I put the procedure of how to verify this bug is
> > > closed:
> > > 
> > > 1. Make sure automake-nativesdk and autotool-nativesdk can be built.
> >                                       ~~~~~~~~ do you mean autoconf?
> 
> Yes. It should be autoconf-nativesdk. Sorry for my typo.
Thanks, Lianhao.

Because I need to focus on POSIX issues, transfer this feature to Wenzong.
Comment 5 Wenzong.Fan 2011-11-20 23:15:32 UTC
Take over this task from Kai Kang, steps to achieve the goal:

1 add autoconf-nativesdk and automake-nativesdk recipes
2 add autoconf-nativesdk and automake-nativesdk to meta-toolchain
3 check the recipes that inherits autotools, 'configure' doesn't show warning
info like:
  WARNING: unrecognized options: --with-libtool-sysroot
Comment 6 Lianhao Lu 2011-11-21 01:22:54 UTC
(In reply to comment #5)
> Take over this task from Kai Kang, steps to achieve the goal:
> 
> 1 add autoconf-nativesdk and automake-nativesdk recipes
> 2 add autoconf-nativesdk and automake-nativesdk to meta-toolchain
> 3 check the recipes that inherits autotools, 'configure' doesn't show warning
> info like:
>   WARNING: unrecognized options: --with-libtool-sysroot

It should use a 3rd party autoconf supported project to test, not the recipes that inherits autotools, which use autoconf/automake-native, not nativesdk. Please see step 3 in my Comment 1.
Comment 7 Wenzong.Fan 2011-11-21 01:39:27 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > Take over this task from Kai Kang, steps to achieve the goal:
> > 
> > 1 add autoconf-nativesdk and automake-nativesdk recipes
> > 2 add autoconf-nativesdk and automake-nativesdk to meta-toolchain
> > 3 check the recipes that inherits autotools, 'configure' doesn't show warning
> > info like:
> >   WARNING: unrecognized options: --with-libtool-sysroot
> 
> It should use a 3rd party autoconf supported project to test, not the recipes
> that inherits autotools, which use autoconf/automake-native, not nativesdk.
> Please see step 3 in my Comment 1.

Thanks for your clarification, Lianhao.
Comment 8 Wenzong.Fan 2011-11-30 17:28:16 UTC
commit 1f2b546f3d65c27f6423695b7e28300565b7afc2
Comment 9 liang li 2011-12-08 01:24:51 UTC
verified on nightly build 20111207-2:
http://autobuilder.pokylinux.org/pub/nightly/20111207-2/toolchain
using  powerpc toolchain and follow test steps below:
1. set build env,run "source /opt/poky/1.1+snapshot/environment-setup-ppc603e-poky-linux".
2. download iptables-1.4.11.tar.bz2 and extract it.
3. run "autoreconf -fi" in the iptable dir.
4. run "./configure ${CONFIGURE_FLAGS}" in the iptable dir.
not met "WARNING: unrecognized options: --with-libtool-sysroot" when run "configure". 

git info :
1.2_M1:b9d3a5224c7f76f273d5919a88b7460d35ad2574