From: Claus Enneper <cl.en@gmx.net>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: quik-1.3.1and 2.2.16_pmac-stable ?
Date: Sat, 17 Jun 2000 02:20:46 +0200 [thread overview]
Message-ID: <20000617022046.C508@olis.north.de> (raw)
In-Reply-To: <20000616233416.1720@mailhost.mipsys.com>; from Benjamin Herrenschmidt on Sat, Jun 17, 2000 at 01:34:16AM +0200
>:
>: Ah, yes, it's a different issue. You should probably use a more recent
>: quik (2.0+) to work with recent kernels. Old quik doesn't like the new
>: kernel entry point (without the pseudo-xcoff hack).
is there any binary available?
quik-2.0-0d.src.rpm from Yellow Dog Linux <bugs@terraplex.com> complains:
make[1]: Entering directory `/usr/src/redhat/BUILD/quik-2.0/util'
gcc -O2 -o elfextract elfextract.c
In file included from /usr/include/linux/elf.h:5,
from elfextract.c:7:
/usr/include/asm/elf.h:43: parse error before `elf_vrreg_t'
/usr/include/asm/elf.h:43: warning: data definition has no type or storage class/usr/include/asm/elf.h:44: parse error before `elf_vrregset_t'
/usr/include/asm/elf.h:44: warning: data definition has no type or storage classmake[1]: *** [elfextract] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/quik-2.0/util'
make: *** [all] Error 1
Bad exit status from /var/tmp/rpm-tmp.35142 (%build)
--
Yours, ce
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-17 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 16:08 quik-1.3.1and 2.2.16_pmac-stable ? Claus Enneper
2000-06-16 23:05 ` Claus Enneper
2000-06-16 23:34 ` Benjamin Herrenschmidt
2000-06-17 0:20 ` Claus Enneper [this message]
2000-06-17 17:55 ` Daniel Jacobowitz
2000-06-18 13:48 ` Claus Enneper
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=20000617022046.C508@olis.north.de \
--to=cl.en@gmx.net \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).