From: Steve Woloschek <steve@zbuda.com>
To: sid@sourceware.org
Subject: Trouble adding additional CPU support
Date: Sun, 21 Sep 2008 21:46:00 -0000 [thread overview]
Message-ID: <1222033611.7469.75.camel@gateway.zbuda.com> (raw)
I have written a new processor description with cgen and I am trying to
update sid to incorporate the new processor.
I have perused the configure.* and Makefile.* files to understand what
changes I need to make in order have the new processor built.
Unfortunately I am not an expert in autoconf and automake and every time
I attempt to rebuild the configure/Makefiles I run into multiple issues.
1) I am not entirely sure which configure.* and Makefile.* need to be
updated to add a new processor.
2) Lack of understanding how to rebuild configure scripts and Makefiles
When trying to rebuild configure scripts and Makefiles it appears there
is a restriction and/or assumption on the particular version of the
tools that required. I have linux box with the latest version of Ubuntu
that I am using as my build machine. I have the following versions of
utilities.
aclocal 1.10.1
autoconf 2.61
automake 1.10.1
libtool 1.5.26
If I remove the restriction of autoconf 2.59 things and try to
regenerate the files I run into several build issues.
It would be very nice if I could use the latest versions of these
utilities to build. U just need the recipe to regenerate the proper
files to build.
Thanks in advance,
Steve
next reply other threads:[~2008-09-21 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 21:46 Steve Woloschek [this message]
2008-09-22 19:51 ` Dave Brolley
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=1222033611.7469.75.camel@gateway.zbuda.com \
--to=steve@zbuda.com \
--cc=sid@sourceware.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).