linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: sting sting <zstingx@hotmail.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: cross-compiling problems (linux to ppc)
Date: Wed, 31 Mar 2004 10:55:39 -0600	[thread overview]
Message-ID: <1080752139.26315.5.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <Sea2-F28k1Ixzl4anSs00047d9a@hotmail.com>


On Wed, 2004-03-31 at 05:17, sting sting wrote:

> Now , I had followed the instructions on :
> http://penguinppc.org/embedded/cross-compiling/

> ../../gcc-3.3.2/gcc/config/rs6000/linux.h:89:20: signal.h: No such file or d
> tory
> In file included from tconfig.h:22,
>                  from ../../gcc-3.3.2/gcc/libgcc2.c:36:
> ../../gcc-3.3.2/gcc/config/rs6000/linux.h:98: error: parse error before "sta
> "
> ../../gcc-3.3.2/gcc/config/rs6000/linux.h:98: warning: no semicolon at end o
> ruct or union

There's a patch you can apply listed on the page (read carefully). It
will only work if you only want to build kernels (i.e. no glibc, no
userspace).

The other alternative is to install *target* kernel headers (not
/usr/include) and build against those. This is just silly if you don't
want glibc, but the toolchain people are apparently too busy to care.

--
Hollis Blanchard
IBM Linux Technology Center


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-03-31 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 11:17 cross-compiling problems (linux to ppc) sting sting
2004-03-31 16:55 ` Hollis Blanchard [this message]
2004-03-31 18:01   ` Mark Guertin

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=1080752139.26315.5.camel@basalt.austin.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=zstingx@hotmail.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 NNTP newsgroup(s).