From: Al Niessner <Al_Niessner@bigfoot.com>
To: gcc-help@gcc.gnu.org
Subject: In the home stretch...
Date: Tue, 07 Mar 2000 18:30:00 -0000 [thread overview]
Message-ID: <38C5BBB9.68258DAB@bigfoot.com> (raw)
I have a powerpc-wrs-vxworks 2.91.66 compiler for VxWorks now that seems
to be working. There is one error in the build that is annoying me:
gcc -c -DCROSS_COMPILE -DIN_GCC -g -O2 -DHAVE_CONFIG_H -DHAIFA
-I. -I../../egcs-1.1.2-vxworks1/gcc
-I../../egcs-1.1.2-vxworks1/gcc/config
../../egcs-1.1.2-vxworks1/gcc/explow.c
../../egcs-1.1.2-vxworks1/gcc/explow.c: In function `emit_stack_save':
../../egcs-1.1.2-vxworks1/gcc/explow.c:889: warning: assignment from
incompatible pointer type
../../egcs-1.1.2-vxworks1/gcc/explow.c: In function
`emit_stack_restore':
../../egcs-1.1.2-vxworks1/gcc/explow.c:970: warning: assignment from
incompatible pointer type
It seems to be okay, but I want to verify that.
Thanks you for all of the previous help.
I will be posting a patch at the end of the week or so.
Al Niessner
WARNING: multiple messages have this Message-ID
From: Al Niessner <Al_Niessner@bigfoot.com>
To: gcc-help@gcc.gnu.org
Subject: In the home stretch...
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38C5BBB9.68258DAB@bigfoot.com> (raw)
Message-ID: <20000401000000.zO0tEjfyjroef3-QfPSaZUdFhrEVPph4P0clZUZyXV8@z> (raw)
I have a powerpc-wrs-vxworks 2.91.66 compiler for VxWorks now that seems
to be working. There is one error in the build that is annoying me:
gcc -c -DCROSS_COMPILE -DIN_GCC -g -O2 -DHAVE_CONFIG_H -DHAIFA
-I. -I../../egcs-1.1.2-vxworks1/gcc
-I../../egcs-1.1.2-vxworks1/gcc/config
../../egcs-1.1.2-vxworks1/gcc/explow.c
../../egcs-1.1.2-vxworks1/gcc/explow.c: In function `emit_stack_save':
../../egcs-1.1.2-vxworks1/gcc/explow.c:889: warning: assignment from
incompatible pointer type
../../egcs-1.1.2-vxworks1/gcc/explow.c: In function
`emit_stack_restore':
../../egcs-1.1.2-vxworks1/gcc/explow.c:970: warning: assignment from
incompatible pointer type
It seems to be okay, but I want to verify that.
Thanks you for all of the previous help.
I will be posting a patch at the end of the week or so.
Al Niessner
next reply other threads:[~2000-03-07 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 18:30 Al Niessner [this message]
2000-04-01 0:00 ` Al Niessner
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=38C5BBB9.68258DAB@bigfoot.com \
--to=al_niessner@bigfoot.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).