From: Olumide <50295@web.de>
To: gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Thu, 20 Jan 2011 17:23:00 -0000 [thread overview]
Message-ID: <4D386FB7.1010407@web.de> (raw)
In-Reply-To: <4D383EFF.1040503@web.de>
On 20/01/2011 13:56, Olumide wrote:
> On 19/01/2011 21:50, David Daney wrote:
>> Some older versions of GCC were broken with versions of texinfo with two
>> digits in part of the version number. I suspect that is the problem you
>> are seeing.
>>
>> What is the output of 'makeinfo --version'? If it is 4.10 or later...
>
>
> oaina@temp2:~$ makeinfo --version
> makeinfo (GNU texinfo) 4.13
>
Good news.
Build was successful -- I think, here's the log file http://goo.gl/SnKsP
(I had to compiled and install textinfo version 4.9 and install the
latest version ncurses in order to compile texinfo.)
I've also to compile a sample plugin following the instructions here
http://download.autodesk.com/us/maya/2011help/index.html?url=./files/API_Writing_a_simple_plugin.htm,topicNumber=d0e657386
, but I got the error message:
error: CPU you selected does not support x86-64 instruction set
I was able to compile and link sample plugin after I removed
-mtune=pentium4 flag.
next prev parent reply other threads:[~2011-01-20 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51 ` Olumide
2011-01-19 16:21 ` Ian Lance Taylor
2011-01-19 16:37 ` Olumide
2011-01-19 16:39 ` Andrew Haley
2011-01-19 17:08 ` Olumide
2011-01-19 17:11 ` Andrew Haley
2011-01-19 20:13 ` Olumide
2011-01-19 21:51 ` David Daney
2011-01-20 13:56 ` Olumide
2011-01-20 17:23 ` Olumide [this message]
2011-01-20 20:04 ` Jonathan Wakely
2011-01-25 10:30 ` Olumide
2011-01-25 10:59 ` Jonathan Wakely
2011-01-25 11:34 ` Olumide
2011-01-25 11:56 ` Jonathan Wakely
2011-01-25 13:51 ` Olumide
2011-01-25 10:59 ` Kai Ruottu
2011-01-19 16:43 ` Cedric Roux
2011-01-19 16:47 ` Jonathan Wakely
2011-01-19 15:19 ` Jeff Law
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=4D386FB7.1010407@web.de \
--to=50295@web.de \
--cc=gcc-help@gcc.gnu.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).