public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jaya Pavan Bhattiprolu <pavanbhattiprolu@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Compiling GCC for different machine on same Architecture
Date: Tue, 02 Sep 2014 15:08:00 -0000	[thread overview]
Message-ID: <CAABpWqfjO6pHBhBLzJTTE0L-SM30fqYwAQdOy61wAkqK9joDvw@mail.gmail.com> (raw)

Hi,

We are trying to build our code base for CentOS 7 machine with x86_64
architecture on CentOS6 with x86_64.

For that we are trying to build a centos7 Toolchain. All the gcc/ld/ar
should be statically linked, so that we are ensuring that it will not
uses any native centos6 stuff.

In this process, we are able to generate statically linked GCC/AR/LD.
But problem was this GCC not generating a statically linked binaries
and fails while checking flags during configure at "checking static
flag -static ".
Due to this while running those binaries it refers to native libgcc and fails.

We are using the below command for configure.
../gcc../configure -prefix=/mnt/data0/toolchain-vm-temp2
--build=x86_64-CentOS7-linux-gnu
-with-sysroot=/mnt/data0/tools/gnutools/toolchain-vm --disable-nls
--disable-multilib --enable-languages=c,c++ --disable-sim
--enable-symvers=gnu --enable__cxa_atexit  --enable-lto --with-gnu-ld
--enable-static

Can Anyone provide solution or how to achieve this task.

--
Thanks,
Pavan Bhattiprolu

             reply	other threads:[~2014-09-02 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 15:08 Jaya Pavan Bhattiprolu [this message]
2014-09-02 15:26 ` Andrew Haley
2014-09-02 16:18   ` Jaya Pavan Bhattiprolu
2014-09-02 16:45     ` Paul Smith

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=CAABpWqfjO6pHBhBLzJTTE0L-SM30fqYwAQdOy61wAkqK9joDvw@mail.gmail.com \
    --to=pavanbhattiprolu@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).