From: Shawn Hooton <shooton@cms.cendant.com>
To: ultralinux@vger.kernel.org
Subject: Re: Problems compiling 2.2.4 Ultrasparc kernel...
Date: Thu, 25 Mar 1999 02:43:48 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92233005314042@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92232769912646@msgid-missing>
I want to apologize to everyone for being an idiot.
I figured that it should be using the sparc64-linux-gcc
compiler. I figured it was getting egcs from my $CC
so I unset all of my build vars, but I think the damage
had already propagated to the makefiles. Sorry.
FYI: uname -a="Linux {hostname} 2.2.0-pre4 #1 Tue Jan 5 17:08:15 CET
1999 sparc64 unknown"
I really appreciate the quick response!!!
David Miller wrote:
>
> Date: Thu, 25 Mar 1999 02:01:30 +0000
> From: Shawn Hooton <shooton@cms.cendant.com>
>
> egcs -O2 -fomit-frame-pointer -funroll-loops -fno-strength-reduce
> -DEXPORT_SYMTAB -c signal.c
>
> It's using the wrong compiler. Does "uname -a" output "sparc64" as
> the cpu type?
>
> Later,
> David S. Miller
> davem@redhat.com
prev parent reply other threads:[~1999-03-25 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-25 2:01 Problems compiling 2.2.4 Ultrasparc kernel Shawn Hooton
1999-03-25 2:17 ` David Miller
1999-03-25 2:43 ` Shawn Hooton [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-92233005314042@msgid-missing \
--to=shooton@cms.cendant.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.