Bug 8423

Summary: adt_installer fails to execute a command "autoreconf"
Product: [Build System, Metadata & Runtime] OE-Core Reporter: baofeng.wang67
Component: devtools / tool chainAssignee: Paul Eggleton <bluelightning>
Status: VERIFIED NOTABUG QA Contact: Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu>
Severity: normal    
Priority: Medium CC: bogdanx.a.voiculescu, meta.mr.watcher, meta.watcher
Version: 1.8   
Target Milestone: 2.1   
Hardware: x86   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
adt installer log containing error message none

Description baofeng.wang67 2015-10-01 08:25:34 UTC 
Created attachment 2779 [details]
adt installer log containing error message

1, download the package tar from http://downloads.yoctoproject.org/releases/yocto/yocto-1.8/adt-installer, unzip and copy folder to $HOME
2, use default adt_installer.conf, run script "./adt_installer" at $HOME/adt-installer
3, choose default location "(default: /opt/poky/1.8):"
choose silent mode: "[ADT_INST] Please enter your selections here:
S"
then check installation log:
./adt_installer: line 185: autoreconf: command not found

I check the script adt-installer near line 185, it reads: 
  echo_info "Configure opkg ...\n"
  autoreconf
  ./configure --prefix=$parent_folder/$LOCAL_OPKG_LOC --with
....

So it seems for some reason the autoreconf is NOT recognised by command prompt.

4, Extra info:
If I rerun the script adt-installer, as opkg has been configured/installed, the error message will NOT show up again.
So my conclusion is that error ONLY happens 1st time you install an ADT tool to a brand new directory.
Comment 1 Paul Eggleton 2015-10-01 08:35:58 UTC 
Did you install the required packages on the test system as noted here:
http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#using-the-adt-installer
?
Comment 2 Paul Eggleton 2015-10-01 14:56:32 UTC 
Marking NEEDINFO as per above comment.
Comment 3 baofeng.wang67 2015-10-01 15:23:16 UTC 
Sorry, seems I forgot to do this.
After running "sudo apt-get install autoconf automake libtool libglib2.0-dev", autoreconf is a known command now.
I will then close the case as an invalid one. Apologise for any extra effort caused by me.
Comment 4 Bogdan Alexandru Voiculescu 2015-11-17 10:15:50 UTC 
not a bug.