Hi Eljay,
Thanks for your help.. I have finally succeeded in
installing Gcc3.2.... :-)..
But all my test suites arent success
when I do make check-gcc RUNTESTFLAGS="execute.exp"
I get
FAIL: gcc.c-torture/execute/20020307-2.c exe
FAIL: gcc.c-torture/execute/20020307-2.c exe
FAIL: gcc.c-torture/execute/20020307-2.c exe
FAIL: gcc.c-torture/execute/20020307-2.c exe
unroll-loops
FAIL: gcc.c-torture/execute/20020307-2.c exe
unroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20020307-2.c exe
any idea why this happens
Thanks
Tina
--- Eljay Love-Jensen <eljay@xxxxxxxxx> wrote:
> Hi Tina,
>
> >is this correct?
>
> No, not entirely. You cannot build in the source
> directory, nor in any subdirectory in the source
> directory.
>
> To build GCC fresh, you need to have a C compiler on
> your computer already. (A chicken-and-egg problem.)
> Do you already have a C compiler?
>
> You also need to delete your source directory, and
> unpack it again from the tar file. Since you
> already tried to build there, it's tainted.
>
> Then do this from the GCC source directory...
>
> % mkdir ../objdir
> % cd ../objdir
> % ../{gcc-source}/configure
>
--enable-languages='all,ada,c,c++,f95,f77,java,objc,obj-c++,treelang'
> --prefix=/home/manas/tina/temp
> --enable-shared
> --enable-threads=posix
> --with-local-prefix=/home/manas/tina/temp/include
> --enable-clocale=gnu --enable-__cxa_atexit
> --disable-libada
>
> The configure being all on one line, of course. So
> you'll be changing directories to a directory that
> is a peer directory to the GCC source.
>
> Note: I've had better luck using full path names
> instead of relative names to get to the configure.
> Most people use relative names, so it's probably
> just something oddball in my environment.
>
> Also, I haven't used Fedora, so if there are
> Fedora-isms involved, I'm not aware of them.
>
> HTH,
> --Eljay
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
