[erlang-questions] unable to build valgrind-enabled erlang runtime
Tue Mar 4 09:45:54 CET 2014
Hello List and Sverker,
Thank you for your assistance. I did have valgrind installed prior to
running configure, but not its source code. Installing the source code and
running configure again did fix the problem of the missing include file
just as you indicated.
However, I am still unable to build the valgrind-enabled emulator due to
occurence of other errors. After calling:
env ERL_TOP=/home/ec2-user/otp_src_R16B02 make valgrind FLAVOR=smp
I receive the following errors:
undefined reference to `nbif_emulate_fpe'
obj/x86_64-unknown-linux-gnu/valgrind/smp/hipe_amd64_bifs.o: In function
undefined reference to `erts_restore_fpu'
collect2: ld returned 1 exit status
make: Leaving directory `/home/ec2-user/otp_src_R16B02/erts/emulator'
Would appreciate any suggestions as to how to fix this.
On Mon, Mar 3, 2014 at 8:45 AM, Sverker Eriksson <
> On 03/01/2014 12:12 AM, Kris Prieb wrote:
>> Hello List,
>> I am attempting to build a valgrind-enabled erlang runtime per:
>> My platform is an amazon linux machine image on ec2 on which I have
>> installed an erlang disribution from source.
>> I entered the following at the command prompt:
>> [ emulator]$ env
>> ERL_TOP=/home/ec2-user/otp_src_R16B02 FLAVOR=smp make valgrind
>> The following was returned:
>> make -f x86_64-unknown-linux-gnu/Makefile TYPE=valgrind
>> can't open x86_64-unknown-linux-gnu/valgrind/plain/erl_compile_flags.h
>> writing at utils/make_compiler_flags line 65.
>> make: Entering directory `/home/ec2-user/otp_src_R16B02/erts/emulator'
>> if utils/gen_git_version x86_64-unknown-linux-gnu/gen_git_version.mk;
>> touch beam/erl_bif_info.c; fi
>> *** valgrind emulator disabled by configure - omitted target all
>> make: Leaving directory `/home/ec2-user/otp_src_R16B02/erts/emulator'
>> What have I done wrong here? Do I have to run "configure" with special
>> arguments before building valgrind-enabled runtime?
>> Any help would be much appreciated!
> If configure does not find a working valgrind, that target will be
> Search for "valgrind" in erts/config.log to see what failed. It probably
> failed to compile #include <valgrind/valgrind.h>.
> If your valgrind is installed in a non-standard place, point it out to
> configure with CPPFLAGS=-I/my/valgrind/install/dir/include.
> /Sverker, Erlang/OTP
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions