Ultralinux archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Uziel <uzi@uzix.org>
To: ultralinux@vger.kernel.org
Subject: Re: Couldn't find sparc64-linux-gcc
Date: Wed, 27 Sep 2000 01:15:18 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-97001720220366@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-96995143407396@msgid-missing>

* YAMAMOTO Taku <yamataku@layer-seven.com> [000926 03:00]:
> [root@xxx linux-2.2.16rh]# rpm -ivh
> /home/yamamoto/archives/kernel/kernel-headers-2.2.16-3.sparc.rpm
> 
> kernel-headers              ##################################################
> You must create /usr/include/asm/asm-sparc* symlinks first.

Hmm... look at the kernel source rpm's specfile to see why it
would give this error.

> /usr/include/bits/ioctl-types.h:25: asm/ioctls.h: No such file or
> directory

Look in /usr/include/asm and see if it's contents are fishy.  It
sounds like you may need to do something like go into /usr/include
and run:

        ln -s /usr/src/linux/include/asm-sparc asm

... or something like that.

> /usr/include/bits/sigcontext.h:28: asm/sigcontext.h: No such file or directory

Same problem again...

> /usr/include/linux/errno.h:4: asm/errno.h: No such file or directory

... and again ...

See if the problem is obvious and fixable... if you continue to have
problems with this, drop me and email and we'll go from there I guess...
-
To unsubscribe from this list: send the line "unsubscribe ultralinux" in
the body of a message to majordomo@vger.kernel.org

      parent reply	other threads:[~2000-09-27  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-26  6:59 Couldn't find sparc64-linux-gcc YAMAMOTO Taku
2000-09-26  7:18 ` Joshua Uziel
2000-09-26  9:59 ` YAMAMOTO Taku
2000-09-27  1:15 ` Joshua Uziel [this message]

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=marc-linux-ultrasparc-97001720220366@msgid-missing \
    --to=uzi@uzix.org \
    --cc=ultralinux@vger.kernel.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