Some messages are Japanese, it means like “ld exited with status1”, “Error 1”, “Error 2”, “Exiting directory …” etc.
Anyone can help me out?
I checked Prerequisites page and found there is not /usr/lib/libXpm.so but /usr/lib/libXpm.so.2, so I made symlink like following,
cd /usr/lib
ln -s libXpm.so.2 libXpm.so
And then did make again but got no luck. I also tried previous version (v5.24.00) but got no luck either.
My environment is following;
[ul]Red Hat Enterprise Linux Server release 5.4 (x86_64)
gcc 4.1.2
Don’t know hardware detail but it is DELL server with 24 core or something[/ul]
Gerri will process your problem once he will be back. Meanwhile do
make -k
the compilation will process till the end, only the xrootd stuff will not be built.
[quote=“furano”]But the strange thing is that the symbols don’t look correct. It is not ‘eadler32’, it should be ‘adler32’. The same for ‘einflate’.
Where can we find such a platform to have a look?[/quote]
It is Red Hat Enterprise Linux Server release 5.4 (x86_64) as I mentioned, but default locale is ja_JP. I think there is not language specific version of RHEL but only universal version and user selects locale at install.
And about symbol, yes it is weired. I investigated a line of source code where error occurs, but there is not ‘eadler32’ but ‘adler32’.
I didn’t think locale affected but tried to build with LANG=C. Same error occured as LANG=ja_JP.UTF-8.
I managed to build successfully though need to do some tricky things.
It seems compiler replaces symbol when header file zlib.h are included from system, but when it is included from ROOT package itself by using -I option then symbol is not replaced. I don’t know why this makes difference for it can be confirmed that they are totaly same by following.
Anyway, below is what I did to build.
First run ‘make’ without ‘-k’ option till error occurs. And then move into directory where error occured and manually compile object file with specifying include directory by -I option.
I’m using Scientific Linux 6 (SL6 with x86_64) and can’t build root from source. I added all the packages listed on root.cern.ch/drupal/content/build-prerequisites and also found that the tetex-latex package is also needed.
However, the root build fails at
g++ -O2 -pipe -m64 -Wshadow -Wall -W -Woverloaded-virtual -fPIC -Iinclude -pthread -I/freetype2 -I -o graf2d/graf/src/TLatex.o -c /root/Cern/root/graf2d/graf/src/TLatex.cxx
g++: graf2d/graf/src/TLatex.o: No such file or directory
make: *** [graf2d/graf/src/TLatex.o] Error 1
Something appears to be missing, but ./configure did not complain.
I don’t know how many other compilation errors there will be beyond TLatex.o. If I knew how to compile TLatex.cxx by hand, I could see how much further the “make” got towards completion.
I’m having the same problem with root 5_32_04 on a SL 5.2 system, gcc 4.5.3:
g++ -O2 -pipe -m64 -Wshadow -Wall -W -Woverloaded-virtual -fPIC -Iinclude -pthread -I/freetype2 -I -o graf2d/graf/src/TLatex.o -c /net/neutrino-fs/raid/genie/root_5_32_04/graf2d/graf/src/TLatex.cxx
g++: graf2d/graf/src/TLatex.o: No such file or directory
It looks like the -I flag is hiding the -o and g++ is interpreting TLatex.o as an input. I suppose the Makefile is autogenerated in some way? Otherwise, how is anyone getting this to build?
Removing the -I gets me to the next line which also has the same error. Fixing it, I get a different error:
g++ -O2 -pipe -m64 -Wshadow -Wall -W -Woverloaded-virtual -fPIC -Iinclude -pthread -I/freetype2 -o graf2d/graf/src/TText.o -c /net/neutrino-fs/raid/genie/root_5_32_04/graf2d/graf/src/TText.cxx
In file included from include/TTF.h:30:0,
from /net/neutrino-fs/raid/genie/root_5_32_04/graf2d/graf/src/TText.cxx:16:
/usr/include/ft2build.h:56:38: fatal error: freetype/config/ftheader.h: No such file or directory
Again, looks like problems with the includes, but perhaps my freetype2 install is non-standard…
It sounds like the configure step and/or the setting up of the variable has not been successful. Can you send us your config.log file and the location (path) of your source and build directory.
I discovered something interesting. In order to solve the freetype problem I reran configure with --enable-builtin-freetype. And, that had the side effect of fixing the original problem with the -I flag hiding the -o.
I’m doing the build at my local institution but can provide a “bad build” sandbox area and a login if you like.
mike
[quote=“pcanal”]Hi,
It sounds like the configure step and/or the setting up of the variable has not been successful. Can you send us your config.log file and the location (path) of your source and build directory.
[quote]'m having the same problem with root 5_32_04 on a SL 5.2 system, gcc 4.5.3:
…
In order to solve the freetype problem I reran configure with --enable-builtin-freetype. And, that had the side effect of fixing the original problem with the -I flag hiding the -o.
[/quote]
I vaguely recollect that we did indeed have such a problem. A priori this is solved in more recent version of ROOT and you may want to try v5.34/07.