From: "Paul D. Smith" <pausmith@nortelnetworks.com>
To: crossgcc@sourceware.cygnus.com
Subject: Re: Building GCC 2.95.2 for VxWorks (powerpc)
Date: Thu, 04 Jan 2001 10:50:00 -0000 [thread overview]
Message-ID: <p5lmsrxic7.fsf@lemming.engeast.baynetworks.com> (raw)
In-Reply-To: <3A536BAB.B4555@sigint.com>
%% Ryan Maples <rmaples@sigint.com> writes:
rm> I have this same setup and have developed a shell script to build
rm> the tool set for me.
Cool. I'll take a look at your script; offhand it doesn't seem much
different than what I did except for the --with-newlib stuff.
I was able to get things to build, although I had to hack a few files
(see my other posts). I will almost definitely end up rebuilding the
cross-compiler again, though, to clean things up.
Were you able to build without changing _any_ files, including the
fdmatch bug and the collect2 stuff, and have it all work?
rm> 6.1. Note. The --with-newlib does not really install or use
rm> newlib. As you can see by the fact that the script does not build
rm> or install the software. The software sources for newlib do not
rm> even exist on the machine I build on.
Then can you tell me why you include --with-newlib?
What does this flag do for the configure and why is it used/needed?
That would be most helpful. Thanks!
rm> The C++ compiler has built successfully many times but I have
rm> never tried to cross compile C++ code for my target.
Ah, this probably explains why you don't need to modify the collect2
stuff. Only if you did use C++, would you run into this problem.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> HASMAT--HA Software Methods & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Paul D. Smith" <pausmith@nortelnetworks.com>
To: crossgcc@sourceware.cygnus.com
Subject: Re: Building GCC 2.95.2 for VxWorks (powerpc)
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <p5lmsrxic7.fsf@lemming.engeast.baynetworks.com> (raw)
Message-ID: <20010401000000.s-RBS8u8nTxGxf1LkJxrICQNm8osASP8ETgRm-0l31A@z> (raw)
In-Reply-To: <3A536BAB.B4555@sigint.com>
%% Ryan Maples <rmaples@sigint.com> writes:
rm> I have this same setup and have developed a shell script to build
rm> the tool set for me.
Cool. I'll take a look at your script; offhand it doesn't seem much
different than what I did except for the --with-newlib stuff.
I was able to get things to build, although I had to hack a few files
(see my other posts). I will almost definitely end up rebuilding the
cross-compiler again, though, to clean things up.
Were you able to build without changing _any_ files, including the
fdmatch bug and the collect2 stuff, and have it all work?
rm> 6.1. Note. The --with-newlib does not really install or use
rm> newlib. As you can see by the fact that the script does not build
rm> or install the software. The software sources for newlib do not
rm> even exist on the machine I build on.
Then can you tell me why you include --with-newlib?
What does this flag do for the configure and why is it used/needed?
That would be most helpful. Thanks!
rm> The C++ compiler has built successfully many times but I have
rm> never tried to cross compile C++ code for my target.
Ah, this probably explains why you don't need to modify the collect2
stuff. Only if you did use C++, would you run into this problem.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith@baynetworks.com> HASMAT--HA Software Methods & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
------
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 prev parent reply other threads:[~2001-01-04 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 23:33 Paul D. Smith
2001-01-03 4:33 ` Kai Ruottu
2001-01-03 8:08 ` Paul D. Smith
2001-01-04 2:55 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Paul D. Smith
2001-04-01 0:00 ` Kai Ruottu
2001-01-03 10:08 ` Ryan Maples
2001-01-04 10:50 ` Paul D. Smith [this message]
2001-04-01 0:00 ` Paul D. Smith
2001-04-01 0:00 ` Ryan Maples
2001-04-01 0:00 ` Paul D. Smith
2001-01-04 3:26 David Korn
2001-04-01 0:00 ` David Korn
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=p5lmsrxic7.fsf@lemming.engeast.baynetworks.com \
--to=pausmith@nortelnetworks.com \
--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).