Can't find dependency


Alex Njaastad
 

I have a packaging file (autoconf) that looks like this:

# abort script on any command that exits with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

export PATH=$PATH:${BOSH_INSTALL_TARGET}/bin:/var/vcap/packages/dynomite1/bin

tar xvf autoconf/autoconf.tar.gz
(
set -e
cd autoconf-2.69
autoconf_dir=$PREFIX/share/autoconf ./configure --prefix=$PREFIX
make
make install prefix=$PREFIX
)

------------------------------------------------------------------------------------------------
Then I have another packaging file (Dynomite) that looks like this:

# abort script on any command that exit with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

tar xvf dynomite1/dynomite.tar.gz
(
set -e
cd dynomite

autoreconf -fvi
CFLAGS="-ggdb3 -O0" ./configure --enable-debug=full --prefix=$PREFIX
make
make install prefix=$PREFIX
)
--------------------------------------------------------------------------------------------------------------
Dynomite has a spec file that looks like this:

---
name: dynomite1
dependencies:
- autoconf
- libtool
files:
- dynomite1/dynomite*
-------------------------------------------------------------------------------------------------------------------------
Dynomite depends on autoconf, as it uses the autoreconf command. When building the packages, the autoreconf command fails, as I get the following error:

"packaging: line 12: autoreconf: command not found"
---------------------------------------------------------------------------------------------------------------------------

What might I be doing wrong?


Dmitriy Kalinin
 

Line "autoreconf -fvi" seems to fail to find autoreconf on path. You may
have to add "export PATH=$PATH:/var/vcap/packages/autoconf/bin" to your
dynomite package.

On Mon, Aug 29, 2016 at 3:51 PM, Alex Njaastad <anjaastad(a)gmail.com> wrote:

I have a packaging file (autoconf) that looks like this:

# abort script on any command that exits with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

export PATH=$PATH:${BOSH_INSTALL_TARGET}/bin:/var/vcap/
packages/dynomite1/bin

tar xvf autoconf/autoconf.tar.gz
(
set -e
cd autoconf-2.69
autoconf_dir=$PREFIX/share/autoconf ./configure --prefix=$PREFIX
make
make install prefix=$PREFIX
)

------------------------------------------------------------
------------------------------------
Then I have another packaging file (Dynomite) that looks like this:

# abort script on any command that exit with a non zero value
set -e
set -x

PREFIX=${BOSH_INSTALL_TARGET}

tar xvf dynomite1/dynomite.tar.gz
(
set -e
cd dynomite

autoreconf -fvi
CFLAGS="-ggdb3 -O0" ./configure --enable-debug=full --prefix=$PREFIX
make
make install prefix=$PREFIX
)
------------------------------------------------------------
--------------------------------------------------
Dynomite has a spec file that looks like this:

---
name: dynomite1
dependencies:
- autoconf
- libtool
files:
- dynomite1/dynomite*
------------------------------------------------------------
-------------------------------------------------------------
Dynomite depends on autoconf, as it uses the autoreconf command. When
building the packages, the autoreconf command fails, as I get the following
error:

"packaging: line 12: autoreconf: command not found"
------------------------------------------------------------
---------------------------------------------------------------

What might I be doing wrong?