From: markm@student.unsw.edu.au
To: crossgcc@sourceware.cygnus.com
Subject: linux i486 -> sparc-solaris2.7 build problems
Date: Thu, 15 Jun 2000 22:52:00 -0000 [thread overview]
Message-ID: <20000616155219.E14110@student.unsw.edu.au> (raw)
Hi,
I was hoping someone could help me with a problem building a cross
compiler for host=i486-pc-linux, target=sparc-sun-solaris2.7
I have looked through archives but didn't seem to find an answer.
0. Got over the MAX_PATH thingy.
1. When in build-gcc/sparc-sun-solaris2.7/libio:
In file included from ../../../gcc-2.95.2/libio/iofscanf.c:25:
../../../gcc-2.95.2/libio/libioP.h:30: errno.h: No such file or
directory
So I added -Ipath_to_solaris_headers (configure didn't seem to do this)
But then I get the following error:
../../../gcc-2.95.2/libio/iofscanf.c: In function \x1fIO_fscanf':
../../../gcc-2.95.2/libio/iofscanf.c:44: \x1f_builtin_va_alist' undeclared
(first use in this function)
(Each undeclared identifier is reported only once
for each function it appears in.)
I am a bit unsure what to do here.
2. Sorry for a dumb question, but the sun identification program
gives SunOS 5.7, but MACHTYPE gives sparc-sun-solaris2.7 Are they
the same?
3. Although I am compiling this to use on a i486, I am using a k6
to build the cross gcc. Why then does configure seem to ignore
i486-pc-linux and use i586 (worried I will be unable to use it)
I am following the cross gcc faq. For both the ix86 host and the
target source, I have binutils_2.9.5.0.22 (hopefully the
2.9.1/solaris bug is fixed) and gcc_2.95.2. on a mouldy debian potato.
Thanks for reading,
Mark.
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-15 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 22:52 markm [this message]
2000-06-16 2:08 ` Kai Ruottu
2000-06-16 15:14 ` markm
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=20000616155219.E14110@student.unsw.edu.au \
--to=markm@student.unsw.edu.au \
--cc=crossgcc@sourceware.cygnus.com \
/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).