search

erlyaws / yaws

Yaws webserver
https://erlyaws.github.io
BSD 3-Clause "New" or "Revised" License
1.28k stars 268 forks source link

Installing from git, using autoconf 2.59, CentOS 5.7 #74

Closed yeysus closed 12 years ago

yeysus commented 12 years ago

Hi. After upgrading Erlang from source to R15B yaws 1.91 stops working. I tried the current yaws git version (23.Dec.2011) but autoconf bombs with an error:

configure.in:219: error: AC_LANG: unknown language: Erlang

autoconf/lang.m4:123: _AC_LANG_SET is expanded from...

autoconf/lang.m4:132: AC_LANG is expanded from...

configure.in:219: the top level

I am on autoconf 2.59, CentOS 5.7. Is a newer autoconf version recommended, or any manual workaround for this? Thanks, Jesus

vinoski commented 12 years ago

autoconf 2.59 is pretty old, as it's from 2003. I believe the Erlang macros were first added in 2006, not sure which version. The Erlang macros also changed somewhat around version 2.63, so I'd recommend getting autoconf version 2.64 or better. I have 2.68 on my development laptop.

Perhaps we need to change the configure.in script in yaws to set a minimum acceptable autoconf version.

yeysus commented 12 years ago

Thanks. autoconf shows me automake, libtool, php-pear, and php53-devel as dependencies. I will see how I can upgrade it w/o breaking things and keep you posted.

yeysus commented 12 years ago

Solved. Installed autoconf 2.68 under a non-standard-directory (/opt/autoconf) so it (hopefully) does not conflict with 2.59, and exported this as PATH before using autoconf in the yaws-git directory. configure is created, configure/make/make install work; yaws is now working as before. Thanks vinoski!. Question: yaws -v still gives 1.91. Is there a way to reflect (yaws -v, yaws -g or something) that this is actually yaws-1.91-git-23.12.2011.17:40 whatever? Regards, Jesus.

yeysus commented 12 years ago

CentOS 5.7, Erlang R15B, yaws 1.92 works (like 1.91-git).

vinoski commented 12 years ago

I think the only way to reflect the current git version is to manually change vsn.mk to include the appropriate information. You could also try building with rebar instead of make, as I think rebar uses the git version by default.