From: Darren Cubbage <darren_cubbage@systemsunion.com>
To: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Linux->sparc-sun-solaris cross compiler
Date: Mon, 28 Feb 2000 02:28:00 -0000 [thread overview]
Message-ID: <1BD9BB6BF02AD211AE2400104B59E64E01651015@RDEX1> (raw)
I am trying tto build a cross-compiler on my linux box for the
sparc-sun-solaris2.7
Steps taken:
i) built the binutils package.
ii) copied the sparc runtime headers and libraries from /usr/include and
/usr/ccs/lib respectively.
iii) ~/gcc-2.95.2/configure --prefix=/home/rddcubba/local/cross-tools
--target=sparc-sun-solaris2.7
iv) make LANGUAGES="c c++" cross
I then get the following error:
/home/rddcubba/build/gcc-2.95/solaris/gcc/xgcc
-B/home/rddcubba/build/gcc-2.95/solaris/gcc/
-B/home/rddcubba/local/cross-tools/sparc-sun-solaris2.7/bin/ -c -g -O2
-fno-implicit-templates -I. -I/home/rddcubba/gcc-2.95.2/libio -nostdinc++
/home/rddcubba/gcc-2.95.2/libio/iostream.cc
/home/rddcubba/gcc-2.95.2/libio/iostream.cc:40: printf.h: No such file or
directory
make[2]: *** [iostream.o] Error 1
make[2]: Leaving directory
`/home/rddcubba/build/gcc-2.95/solaris/sparc-sun-solaris2.7/libio'
make[1]: *** [all-target-libio] Error 2
make[1]: Leaving directory `/home/rddcubba/build/gcc-2.95/solaris'
On searching on the sun box, I cannot find a printf.h file. I have searched
through the help archives but cannott find any help in relation to this
specific problem.
Any help greatly appreciated.
Darren Cubbage
WARNING: multiple messages have this Message-ID
From: Darren Cubbage <darren_cubbage@systemsunion.com>
To: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Linux->sparc-sun-solaris cross compiler
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <1BD9BB6BF02AD211AE2400104B59E64E01651015@RDEX1> (raw)
Message-ID: <20000401000000.k4DMrdEA1xHkuza_YlSLmLyfqx73jSUTHmvYoBayp20@z> (raw)
I am trying tto build a cross-compiler on my linux box for the
sparc-sun-solaris2.7
Steps taken:
i) built the binutils package.
ii) copied the sparc runtime headers and libraries from /usr/include and
/usr/ccs/lib respectively.
iii) ~/gcc-2.95.2/configure --prefix=/home/rddcubba/local/cross-tools
--target=sparc-sun-solaris2.7
iv) make LANGUAGES="c c++" cross
I then get the following error:
/home/rddcubba/build/gcc-2.95/solaris/gcc/xgcc
-B/home/rddcubba/build/gcc-2.95/solaris/gcc/
-B/home/rddcubba/local/cross-tools/sparc-sun-solaris2.7/bin/ -c -g -O2
-fno-implicit-templates -I. -I/home/rddcubba/gcc-2.95.2/libio -nostdinc++
/home/rddcubba/gcc-2.95.2/libio/iostream.cc
/home/rddcubba/gcc-2.95.2/libio/iostream.cc:40: printf.h: No such file or
directory
make[2]: *** [iostream.o] Error 1
make[2]: Leaving directory
`/home/rddcubba/build/gcc-2.95/solaris/sparc-sun-solaris2.7/libio'
make[1]: *** [all-target-libio] Error 2
make[1]: Leaving directory `/home/rddcubba/build/gcc-2.95/solaris'
On searching on the sun box, I cannot find a printf.h file. I have searched
through the help archives but cannott find any help in relation to this
specific problem.
Any help greatly appreciated.
Darren Cubbage
next reply other threads:[~2000-02-28 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 2:28 Darren Cubbage [this message]
2000-02-28 15:09 ` Martin v. Loewis
2000-04-01 0:00 ` Martin v. Loewis
2000-02-28 23:54 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Darren Cubbage
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=1BD9BB6BF02AD211AE2400104B59E64E01651015@RDEX1 \
--to=darren_cubbage@systemsunion.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).