erlsom @1.2.1_1 Configure error causes build failure

[afbrand@…]

Erlsom build fails during the configure phase. It reports that that the dependency Erlang is broken, citing a missing path. Nevertheless, the path exists and Erlang executes normally.

The configure.log error line reads:

configure:1920: error: Broken Erlang installation, "/opt/local/lib/erlang" does not exist!

Erlang not only exists, but this path is valid and Erlang runs normally.

[afbrand@…]

Erlsom build configuration log file.

[afbrand@…]

Erlsom build main log file.

[mf2k (Frank Schima)]

In the future, please use WikiFormatting.

[ryandesign (Ryan Carsten Schmidt)]

I see from your main.log that you're using trace mode. Does the problem persist when not using trace mode?

[afbrand@…]

Replying to ryandesign@…:

I see from your main.log that you're using trace mode. Does the problem persist when not using trace mode?

Yes, the same thing happens. I have trace on, because I believe I saw somewhere in the docs that recommended it. The suggestion was that a traced log was more helpful for those troubleshooting a ticket.

[ryandesign (Ryan Carsten Schmidt)]

Ok, I see this too.

The problem is that erlsom's configure script just reads the erl launcher script and takes all the characters after ROOTDIR= as the path to use. The problem is that in erlang 18.3, the line in the erl script reads:

ROOTDIR="/opt/local/lib/erlang"

erlsom's configure script is therefore taking "/opt/local/lib/erlang" -- with the quotation marks -- as the path to use, and that path does not exist. Maybe previous versions of erlang did not enclose the path in quotation marks and therefore didn't expose this problem.

[ryandesign (Ryan Carsten Schmidt)]

r148428

[afbrand@…]

Installed erlsom without a problem.

Thank you.