Discussion:
Compile Error: No rule to make target 'am--refresh'
Willy Mularto
2018-03-03 17:41:04 UTC
Permalink
Hi list,
I'm not sure what's going on, I just tried to install Kannel (snapshot
version) on to a fresh Ubuntu LTS 16.04 (Xenial Xerus), somehow it stop
during make with error: "No rule to make target 'am--refresh'". Does
anybody experience this error? Any solution to this matter? Thanks.
a***@kannel.org
2018-03-05 12:22:17 UTC
Permalink
Hi,

please call: ./bootstrap.sh before configure.

Thanks,
Alex
Post by Willy Mularto
Hi list,
I'm not sure what's going on, I just tried to install Kannel (snapshot version) on to a fresh Ubuntu LTS 16.04 (Xenial Xerus), somehow it stop during make with error: "No rule to make target 'am--refresh'". Does anybody experience this error? Any solution to this matter? Thanks.
Willy Mularto
2018-03-05 12:25:48 UTC
Permalink
Hi,
Thanks, already resolved by doing libtoolize --force.
Post by a***@kannel.org
Hi,
please call: ./bootstrap.sh before configure.
Thanks,
Alex
Post by Willy Mularto
Hi list,
I'm not sure what's going on, I just tried to install Kannel (snapshot
version) on to a fresh Ubuntu LTS 16.04 (Xenial Xerus), somehow it stop
during make with error: "No rule to make target 'am--refresh'". Does
anybody experience this error? Any solution to this matter? Thanks.
Stipe Tolj
2018-03-05 13:01:36 UTC
Permalink
Post by a***@kannel.org
Hi,
please call: ./bootstrap.sh before configure.
Alex,

shouldn't we commit one output instance of the bootstrap.sh output files
to svn trunk so people can build without running into this?
--
Best Regards,
Stipe Tolj

-------------------------------------------------------------------
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/ http://www.tolj.org/

stolj at kannel.org st at tolj.org
-------------------------------------------------------------------
Stipe Tolj
2018-03-06 10:51:10 UTC
Permalink
Hi,
we have to delete configure and stuff because it should not be there only in the release tar archive.
ok, agree. Let's add this to an BUILD file so people know how to deal
with it when they do svn trunk checkouts.

Shall I proceed and also roll for a new devel release? I guess we want
to go for the 1.6.0 branch rather then staying in 1.5.x.

Any objections?

Cheers,
Stipe
--
Best Regards,
Stipe Tolj

-------------------------------------------------------------------
Düsseldorf, NRW, Germany

Kannel Foundation tolj.org system architecture
http://www.kannel.org/ http://www.tolj.org/

stolj at kannel.org st at tolj.org
-------------------------------------------------------------------
a***@kannel.org
2018-03-06 15:24:03 UTC
Permalink
no objections, go for it.

Thanks,
Alex
Hi,
we have to delete configure and stuff because it should not be there only in the release tar archive.
ok, agree. Let's add this to an BUILD file so people know how to deal with it when they do svn trunk checkouts.
Shall I proceed and also roll for a new devel release? I guess we want to go for the 1.6.0 branch rather then staying in 1.5.x.
Any objections?
Cheers,
Stipe
--
Best Regards,
Stipe Tolj
-------------------------------------------------------------------
Düsseldorf, NRW, Germany
Kannel Foundation tolj.org system architecture
http://www.kannel.org/ http://www.tolj.org/
stolj at kannel.org st at tolj.org
-------------------------------------------------------------------
Loading...