public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "tsah marco" <tsahmarco@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: building gcc compiler --target=x86_64
Date: Mon, 31 Dec 2007 13:54:00 -0000	[thread overview]
Message-ID: <23dcc150712310554p54ea44a9hd049a2a83bf13da6@mail.gmail.com> (raw)

hi,

i am trying to build gcc compiler on pc(turion64x2 with fedora-8) for
target - athlon     64bit x2,
i have build one compiler with the following parameters:

[root@localhost gcc-4.1.0]# gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ./configure --enable-languages=c,c++
--enable-threads=posix --disable-checking --enable-__cxa_atexit
--disable-libunwind-exceptions --prefix=/opt/gcc/gcc-4.1.0
Thread model: posix
gcc version 4.1.0

now i want to install   gcc 64bit version the way is to change  the
--target=x86_64--pc-linux-gnu
 in the confiigure script i have som questions:
1)           how   do i     know if my OS fedora-8  is 64bit
based(because  i install x86_64 version      DVD)
2)  i believe gcc version   4.1.0    support 64 bit ,is it   true?
3) do you have  any      configure   example for x86_64 bit that works for you?

i have used  this configure and got an error in the make.
--
./configure --target=x86_64-pc-linux-gnu --enable-languages=c,c++
--enable-threads=posix --disable-checking --enable-__cxa_atexit
--disable-libunwind-exceptions --prefix=/opt/gcc/second_gcc-4.1.0/
--


and then    run
make

the output error after 7 minutes:

            /opt/gcc/second_gcc-4.1.0//lib/gcc/x86_64-pc-linux-gnu/4.1.0/../../../../x86_64-pc-linux-gnu/sys-include
 )
Fixing headers into /opt/gcc/second_gcc-4.1.0/gcc-4.1.0/gcc/include
for x86_64-pc-linux-gnu target
No forbidden identifiers defined by this target
rm -f include/syslimits.h
if [ -f include/limits.h ]; then \
          mv include/limits.h include/syslimits.h; \
        else \
          cp ../.././gcc/gsyslimits.h include/syslimits.h; \
        fi
chmod a+r include/syslimits.h
echo timestamp > stmp-fixinc
rm -f mm_malloc.h
cat ../.././gcc/config/i386/pmm_malloc.h > mm_malloc.h
if [ -f /opt/gcc/second_gcc-4.1.0//lib/gcc/x86_64-pc-linux-gnu/4.1.0/../../../../x86_64-pc-linux-gnu/sys-include/limits.h
] ; then \
          cat ../.././gcc/limitx.h ../.././gcc/glimits.h
../.././gcc/limity.h > tmp-xlimits.h; \
        else \
          cat ../.././gcc/glimits.h > tmp-xlimits.h; \
        fi
mv tmp-xlimits.h xlimits.h
if [ -d include ] ; then true; else mkdir include; chmod a+rx include; fi
for file in .. ../.././gcc/ginclude/float.h
../.././gcc/ginclude/iso646.h ../.././gcc/ginclude/stdarg.h
../.././gcc/ginclude/stdbool.h ../.././gcc/ginclude/stddef.h
../.././gcc/ginclude/varargs.h ../.././gcc/config/i386/mmintrin.h
../.././gcc/config/i386/mm3dnow.h ../.././gcc/config/i386/xmmintrin.h
../.././gcc/config/i386/emmintrin.h
../.././gcc/config/i386/pmmintrin.h mm_malloc.h; do \
          if [ X$file != X.. ]; then \
            realfile=`echo $file | sed -e 's|.*/\([^/]*\)$|\1|'`; \
            echo timestamp > include/$realfile; \
            rm -f include/$realfile; \
            cp $file include; \
            chmod a+r include/$realfile; \
          fi; \
        done
rm -f include/limits.h
cp xlimits.h include/limits.h
cp ../.././gcc/unwind-generic.h include/unwind.h
chmod a+r include/limits.h
rm -f include/README
cp ../.././gcc/../fixincludes/README-fixinc include/README
chmod a+r include/README
echo timestamp > stmp-int-hdrs
make[2]: *** No rule to make target
`/opt/gcc/second_gcc-4.1.0//bin/x86_64-pc-linux-gnu-as', needed by
`stamp-as'.  Stop.
make[2]: Leaving directory
`/opt/gcc/second_gcc-4.1.0/gcc-4.1.0/host-i686-pc-linux-gnu/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/opt/gcc/second_gcc-4.1.0/gcc-4.1.0'
make: *** [all] Error 2





thanks


tsah
Marco
Cel - 972-54-5414357
Home - 972-774240642
Fax - 972-77-4240642

             reply	other threads:[~2007-12-31 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31 13:54 tsah marco [this message]
2007-12-31 16:22 ` Andrew Haley
2008-01-05 14:34 ` Tim Prince

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23dcc150712310554p54ea44a9hd049a2a83bf13da6@mail.gmail.com \
    --to=tsahmarco@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).