Re: [rvm-research] Jikes RVM build problem - Invalid configuration `x86_64-unknown-linux-': machine `x86_64-unknown-linux' not recognized

Rajika Kumarasiri <[email protected]>
Newsgroups gmane.comp.java.jikes.rvm.devel
Message-ID <CAPDRHiYF=qPpRz24gScHOwmycK-aqSiid+sLfYyr9QUXG4uW8g@mail.gmail.com>
I compiled the platform successfully from the ant build file. That required
me to install 32 bit version of some of the libraries into the system. See
below for the list. I hope someone will find this useful.

yum install glibc.i686 glibc-devel.i686 glibc-static.x86_64
glibc-static.i686

Rajika

On Sat, Feb 23, 2013 at 11:11 PM, Rajika Kumarasiri <
[email protected]> wrote:

> hello,
>
> Thank you for your reply and sorry for the delay in getting back. Your
> reply helps.
>
> I successfully ran the configure script with the following options;
>
> $./configure --disable-plugin
>
> Then I tried to use the generated make file but following was the out put,
> it complais that
> /../../native/jni/native-lib  -W -Wall -Wmissing-declarations
> -Wwrite-strings -Wmissing-prototypes -Wno-long-long -Wstrict-prototypes
> -pedantic -Werror -g -O2 -MT jnilink.lo -MD -MP -MF .deps/jnilink.Tpo -c -o
> jnilink.lo jnilink.c
>  gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include
> -I../../../native/jni/classpath -I../../../native/jni/native-lib -W -Wall
> -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes -Wno-long-long
> -Wstrict-prototypes -pedantic -Werror -g -O2 -MT jnilink.lo -MD -MP -MF
> .deps/jnilink.Tpo -c jnilink.c  -fPIC -DPIC -o .libs/jnilink.o
> mv -f .deps/jnilink.Tpo .deps/jnilink.Plo
> /bin/sh ../../../libtool --tag=CC   --mode=link gcc -W -Wall
> -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes -Wno-long-long
> -Wstrict-prototypes -pedantic -Werror -g -O2 -no-undefined  -o
> libclasspath.la  jcl.lo jnilink.lo
> ar cru .libs/libclasspath.a .libs/jcl.o .libs/jnilink.o
> ranlib .libs/libclasspath.a
> creating libclasspath.la
> (cd .libs && rm -f libclasspath.la && ln -s ../libclasspath.la
> libclasspath.la)
> make[3]: Leaving directory
> `/home/rajika/project/jikesrvm/components/classpath/97.2p13/classpath/native/jni/classpath'
> Making all in native-lib
> make[3]: Entering directory
> `/home/rajika/project/jikesrvm/components/classpath/97.2p13/classpath/native/jni/native-lib'
> /bin/sh ../../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../../../include  -I../../../include -I../../../native/jni/classpath
> -I../../../native/jni/native-lib  -W -Wall -Wmissing-declarations
> -Wwrite-strings -Wmissing-prototypes -Wno-long-long -Wstrict-prototypes
> -pedantic -Werror -g -O2 -MT cpnet.lo -MD -MP -MF .deps/cpnet.Tpo -c -o
> cpnet.lo cpnet.c
> mkdir .libs
>  gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../include
> -I../../../native/jni/classpath -I../../../native/jni/native-lib -W -Wall
> -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes -Wno-long-long
> -Wstrict-prototypes -pedantic -Werror -g -O2 -MT cpnet.lo -MD -MP -MF
> .deps/cpnet.Tpo -c cpnet.c  -fPIC -DPIC -o .libs/cpnet.o
> cpnet.c: In function ‘cpnet_addMembership’:
> cpnet.c:583:32: error: dereferencing type-punned pointer will break
> strict-aliasing rules [-Werror=strict-aliasing]
> cpnet.c: In function ‘cpnet_dropMembership’:
> cpnet.c:598:32: error: dereferencing type-punned pointer will break
> strict-aliasing rules [-Werror=strict-aliasing]
> cc1: all warnings being treated as errors
> make[3]: *** [cpnet.lo] Error 1
> make[3]: Leaving directory
> `/home/rajika/project/jikesrvm/components/classpath/97.2p13/classpath/native/jni/native-lib'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/home/rajika/project/jikesrvm/components/classpath/97.2p13/classpath/native/jni'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/home/rajika/project/jikesrvm/components/classpath/97.2p13/classpath/native'
> make: *** [all-recursive] Error 1
>
>
>
>
> On Tue, Feb 19, 2013 at 8:12 AM, Swarnendu Biswas <
> [email protected]> wrote:
>
>>  Hi Rajika,
>> *
>> *Make sure you have automake and autoconf installed. Then, you can try
>> running aclocal, automake, etc. from their individual directories and get
>> them built successfully. You may have to use --disable-gtk-peer option with
>> ./configure, but gtk is probably required for aclocal to build. I think
>> this is what I had to do
>>
>> *cd $jikesrvm_base$/components/classpath/97xxxxx/classpath
>>
>> aclocal -I m4 ----- to generate the aclocal.m4 file
>>
>> autoscan  ---- creates configure.ac
>>
>> autoconf
>>
>> ./configure
>>
>> automake -a --force --copy --foreign
>>
>> References:
>> http://www.linuxselfhelp.com/gnu/autoconf/html_chapter/autoconf_3.html
>>
>> http://www.openismus.com/documents/linux/automake/automake*
>>
>> You can also use
>> libtoolize --copy --force --install --automake
>>
>>
>> --Regards,
>> Swarnendu Biswas,
>> The Ohio State University.
>>
>>
>>
>>  On 02/19/2013 03:25 AM, Erik Brangs wrote:
>>
>> Hi,
>>
>> On 19.02.2013 05:52, Rajika Kumarasiri wrote:
>>
>>  hello,
>>
>> I downloaded the script - fix_x86_64-unknown-linux-gnu.sh
>> to jikesrvm/components/classpath/97.2p13/classpath and ran the script
>> from there. Below is the result.
>> [...]configure.ac:455 <http://configure.ac:455> <http://configure.ac:455>: required file
>> `./config.rpath' not found
>> doc/api/Makefile.am:1: CREATE_API_DOCS does not appear in AM_CONDITIONAL
>> doc/api/Makefile.am:9: CREATE_API_DOCS does not appear in AM_CONDITIONAL
>> doc/api/Makefile.am:39: CREATE_API_DOCS does not appear in AM_CONDITIONAL
>> lib/Makefile.am:30: INSTALL_GLIBJ_ZIP does not appear in AM_CONDITIONAL
>> lib/Makefile.am:36: BUILD_CLASS_FILES does not appear in AM_CONDITIONAL
>> lib/Makefile.am:40: INSTALL_CLASS_FILES does not appear in AM_CONDITIONAL
>> lib/Makefile.am:106: REGEN_PARSERS does not appear in AM_CONDITIONAL
>> ./fix_x86_64-unknown-linux-gnu.sh: automake failed
>>
>>  IIRC some of the potential problems with running the script
>> "fix_x86_64-unknown-linux-gnu.sh" (including the one you posted) are
>> covered in the comment section of the blogpost that linked to the script.
>>
>> I can't give you any further advice regarding autotools because I'm not
>> familiar with autotools.
>>
>>
>>  I have the gcc and g++ development packages installed.
>>
>>  I don't use Fedora so I can't tell you whether those packages include
>> gcc multilib and g++ multilib. Please ensure that you have the multilibs
>> installed.
>>
>>
>> Kind regards,
>>
>> Erik Brangs
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:http://p.sf.net/sfu/appdyn_d2d_feb
>> _______________________________________________
>> Jikesrvm-researchers mailing [email protected]://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_feb
>> _______________________________________________
>> Jikesrvm-researchers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
>>
>>
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb

_______________________________________________
Jikesrvm-researchers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.