Maybe we should modify the configure file to prevent configure and
building open64 in top of trunk directory.

On Wed, Oct 20, 2010 at 5:36 PM, Gang Yu <yugang...@gmail.com> wrote:
> Hi, Yongchong:
>
>   Thanks! It now works.  The key point here is that created build dir be put
> under trunk.
>
> Gang
>
>
> On Wed, Oct 20, 2010 at 5:13 PM, Wu Yongchong <wuyongch...@gmail.com> wrote:
>>
>> In current build process, we use gcc and gfortran to build the main
>> component of open64, and then use the built open64 to build libraries.
>> Some component like the c and c++ front end can only build by gcc, and
>> some library can only be build by open64, so maybe you should not use
>> --with-build-compiler arg and try again.
>>
>> On Wed, Oct 20, 2010 at 5:06 PM, Hucheng Zhou <zhou.huch...@gmail.com>
>> wrote:
>> > When I switch the --with-build-compiler=OSP
>> > with --with-build-compiler=GNU,
>> > the previous error disappears, but it seems that gfortran still cannot
>> > be
>> > used to build mfe95?
>> > ../fe90/fe90.a(fold.o): In function `fold_operation':
>> >
>> > /home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1076:
>> > undefined reference to `_gfortran_selected_real_kind'
>> >
>> > /home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1078:
>> > undefined reference to `_gfortran_selected_real_kind'
>> >
>> > /home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1081:
>> > undefined reference to `_gfortran_selected_real_kind'
>> >
>> > /home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1194:
>> > undefined reference to `_gfortran_selected_real_kind'
>> >
>> > /home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1196:
>> > undefined reference to `_gfortran_selected_real_kind'
>> >
>> > ../fe90/fe90.a(fold.o):/home/zhc/open64-build/osprey/../../trunk/osprey/crayf90/fe90/fold.f:1199:
>> > more undefined references to `_gfortran_selected_real_kind' follow
>> > collect2: ld returned 1 exit status
>> > make[2]: *** [mfef95] Error 1
>> > make[2]: Leaving directory
>> > `/home/zhc/open64-build/osprey/targdir/crayf90/sgi'
>> > make[1]: *** [default] Error 2
>> > make[1]: Leaving directory
>> > `/home/zhc/open64-build/osprey/targdir/crayf90/sgi'
>> > make: *** [first] Error 2
>> > Thanks.
>> > On Wed, Oct 20, 2010 at 4:30 PM, Hucheng Zhou <zhou.huch...@gmail.com>
>> > wrote:
>> >>
>> >> I met another error:
>> >> build/vec.o: In function `gs_decl_global_ctor_p':
>> >>
>> >> hpc17.(none):/home/zhc/open64-build/osprey-gcc-4.2.0/gcc/gspin-tel.h:1020:
>> >> undefined reference to `gs_assert'
>> >> build/vec.o: In function `gs_decl_global_dtor_p':
>> >>
>> >> hpc17.(none):/home/zhc/open64-build/osprey-gcc-4.2.0/gcc/gspin-tel.h:1021:
>> >> undefined reference to `gs_assert'
>> >> build/vec.o: In function `gs_decl_one_only':
>> >>
>> >> hpc17.(none):/home/zhc/open64-build/osprey-gcc-4.2.0/gcc/gspin-tel.h:1022:
>> >> undefined reference to `gs_assert'
>> >>
>> >>
>> >> build/vec.o:hpc17.(none):/home/zhc/open64-build/osprey-gcc-4.2.0/gcc/gspin-tel.h:1023:
>> >> more undefined references to `gs_assert' follow
>> >> collect2: ld returned 1 exit status
>> >> make[4]: *** [build/genconstants] Error 1
>> >> make[4]: Leaving directory
>> >> `/home/zhc/open64-build/osprey-gcc-4.2.0/gcc'
>> >> My configure command is:
>> >> ../trunk/configure --prefix=/home/zhc/open64-install
>> >> --with-build-compiler=OSP --with-build-optimize=DEBUG
>> >> Thanks.
>> >> On Wed, Oct 20, 2010 at 4:13 PM, Gang Yu <yugang...@gmail.com> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>>    Does anyone have meet the problem of compiling current svn
>> >>> version(r3378)? I always get in trouble in the compiling:
>> >>>
>> >>> 1.  the makefile caused link err when building gcc
>> >>> gcc: ../../osprey/targdir/libspin_4_2_0/libgspin42.a: No such file or
>> >>> directory
>> >>> make[4]: *** [cc1-dummy] Error 1
>> >>> make[4]: Leaving directory
>> >>>
>> >>> `/home/yugang/open64-trunk/build/osprey-gcc-4.2.0/host-x86_64-redhat-linux/gcc'
>> >>> make[3]: *** [all-gcc] Error 2
>> >>> make[3]: Leaving directory
>> >>> `/home/yugang/open64-trunk/build/osprey-gcc-4.2.0'
>> >>> make[2]: *** [all] Error 2
>> >>> make[2]: Leaving directory
>> >>> `/home/yugang/open64-trunk/build/osprey-gcc-4.2.0'
>> >>> make[1]: *** [osprey-gcc-4.2.0/gcc/cc1] Error 2
>> >>> make[1]: Leaving directory `/home/yugang/open64-trunk/build'
>> >>>
>> >>> If I patch the osprey-gcc-4.2.0/host-x86_64-redhat-linux/gcc/Makefile
>> >>> with line 851
>> >>> -LIBGSPIN = ../../osprey/targdir/libspin_4_2_0/libgspin42.a
>> >>> +LIBGSPIN = ../../../osprey/targdir/libspin_4_2_0/libgspin42.a
>> >>> will make it work.
>> >>>
>> >>> 2. building the lib with opencc(SELF):
>> >>> make  libopen64rt.a
>> >>> C
>> >>>
>> >>> /home/administrator/open64-trunk/trunk/osprey/targdir_lib/libopen64rt/../../../osprey/libopen64rt/malloc_opt.c
>> >>> opencc ERROR: cannot exec
>> >>>
>> >>> /home/administrator/open64-trunk/trunk/osprey/.././osprey-gcc-4.2.0/gcc/xgcc:
>> >>> No such file or directory
>> >>> opencc ERROR: cannot exec
>> >>>
>> >>> /home/administrator/open64-trunk/trunk/osprey/.././osprey-gcc-4.2.0/gcc/xgcc:
>> >>> No such file or directory
>> >>> make[3]: *** [malloc_opt.o] Error 1
>> >>> make[2]: *** [default] Error 2
>> >>> make[1]: *** [libopen64rt] Error 2
>> >>> make[1]: Leaving directory
>> >>> `/home/administrator/open64-trunk/trunk/osprey/targdir_lib'
>> >>> make: *** [lib] Error 2
>> >>>
>> >>>
>> >>>
>> >>> environments and configurations will fall into these issues:
>> >>> (1). a linux destop with intel core2(2) 6600 , gcc 4.1.1, kernel
>> >>> 2.6.18
>> >>>          configured with debug , non debug
>> >>>       compiling source under a mirrored dir
>> >>> (2). a ubuntu10 laptop with intel core2 T7250, gcc 4.4.3, kernel
>> >>> 2.6.32
>> >>>          configured with debug, non debug
>> >>>       compiling under a mirror dir or directly in targdir
>> >>> (3). TOOLROOT cleaned
>> >>>
>> >>> Please help.
>> >>>
>> >>> Thanks
>> >>>
>> >>> Gang
>> >>>
>> >>>
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> Download new Adobe(R) Flash(R) Builder(TM) 4
>> >>> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
>> >>> Flex(R) Builder(TM)) enable the development of rich applications that
>> >>> run
>> >>> across multiple browsers and platforms. Download your free trials
>> >>> today!
>> >>> http://p.sf.net/sfu/adobe-dev2dev
>> >>> _______________________________________________
>> >>> Open64-devel mailing list
>> >>> Open64-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/open64-devel
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Institute of High Performance Computing,
>> >>
>> >> Department of Computer Science and Technology,
>> >>
>> >> Tsinghua University, Beijing, China, 100084.
>> >
>> >
>> >
>> > --
>> > Institute of High Performance Computing,
>> >
>> > Department of Computer Science and Technology,
>> >
>> > Tsinghua University, Beijing, China, 100084.
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Download new Adobe(R) Flash(R) Builder(TM) 4
>> > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
>> > Flex(R) Builder(TM)) enable the development of rich applications that
>> > run
>> > across multiple browsers and platforms. Download your free trials today!
>> > http://p.sf.net/sfu/adobe-dev2dev
>> > _______________________________________________
>> > Open64-devel mailing list
>> > Open64-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/open64-devel
>> >
>> >
>>
>>
>>
>> --
>> yongchong
>
>



-- 
yongchong

------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel

Reply via email to