How to compile GCC 4.7.1 on IRIX
#1
How to compile GCC 4.7.1 on IRIX
Moved here: http://forums.irix.cc/thread-207.html

Octane Aezora - Octane - 2xR12k 400 MHz - V8 Graphics - 1216 MB RAM - 6.5.30
O2 Kiki - O2 - R5k 200 MHz - 128 MB RAM - 6.5.30
Two O350 modules Calcifer - Origin 300 - 4xR14k 500 MHz - 2 GB RAM - 6.5.30
Two O350 modules Tohru - Origin 350 - 4xR16k 800 MHz - 4 GB RAM - 6.5.30 - on loan from Raion
Indy Gary - Indy - R5k 180 MHz - 24-bit XL Graphics -  192 MB RAM - 6.5.22
Mirrors
(This post was last modified: 11-03-2018, 06:44 AM by LarBob.)
LarBob
Global Moderator
******

Posts: 89
Threads: 20
Joined: Dec 2017
Find Reply
06-03-2018, 12:31 AM
#2
Re: How to compile GCC 4.7.1 on IRIX
He is correct. irisware uses /opt/local

The magma of our souls burns with a mighty flame! Gurren Lagann! Just who in the hell do you think we are!?

Proud member of Team Gurren, the founder, operator, and developer behind IRIX Network. 

I'm carrying on Pete's legacy, and while I'm not perfect, I'm the only man for the job. Believe in yourself. Not in the you who believes in me. Not the me who believes in you. Believe in the you who believes in yourself.

[Image: daigurrensig.png]
Raion
Operator
*******

Posts: 418
Threads: 82
Joined: Nov 2017
Website Find Reply
06-03-2018, 12:43 AM
#3
Re: How to compile GCC 4.7.1 on IRIX
<QUOTE author="LarBob">
LarBob Wrote:IMPORTANT NOTE: We don't have getopt_long. Before compiling:
* delete D["HAVE_GETOPT_H"]=" 1" line in config.status
* edit config.h + src/ppl.hh.dist to change lines w/ HAVE_GETOPT_H to comments

Brent Canavan has raised this issue in a recent portability track of iperf3
He has found a portable BSD License solution: <URL url="https://github.com/kimgr/getopt_port">https://github.com/kimgr/getopt_port. Build it with cmake (bump VERSION in CMakeLists.txt down to 2.8, since 3.3 doesn't compile cleanly yet)
Getting it inside ppl should not be too much work, but try to see if you can live without this first.
dexter1
Global Moderator
******

Posts: 189
Threads: 10
Joined: May 2018
Find Reply
06-03-2018, 10:27 AM
#4
Re: How to compile GCC 4.7.1 on IRIX
<QUOTE author="dexter1" post_id="707" time="1528021638" user_id="141">
dexter1 post_id=707 time=1528021638 user_id=141 Wrote:<QUOTE author="LarBob">
LarBob Wrote:IMPORTANT NOTE: We don't have getopt_long. Before compiling:
* delete D["HAVE_GETOPT_H"]=" 1" line in config.status
* edit config.h + src/ppl.hh.dist to change lines w/ HAVE_GETOPT_H to comments

Brent Canavan has raised this issue in a recent portability track of iperf3
He has found a portable BSD License solution: <URL url="https://github.com/kimgr/getopt_port">https://github.com/kimgr/getopt_port. Build it with cmake (bump VERSION in CMakeLists.txt down to 2.8, since 3.3 doesn't compile cleanly yet)
Getting it inside ppl should not be too much work, but try to see if you can live without this first.

I get:
Code:
g++      -64  CMakeFiles/cmTryCompileExec2716276232.dir/testCXXCompiler.cxx.o  -o cmTryCompileExec2716276232
g++: error: unrecognized command line option '-64'

Octane Aezora - Octane - 2xR12k 400 MHz - V8 Graphics - 1216 MB RAM - 6.5.30
O2 Kiki - O2 - R5k 200 MHz - 128 MB RAM - 6.5.30
Two O350 modules Calcifer - Origin 300 - 4xR14k 500 MHz - 2 GB RAM - 6.5.30
Two O350 modules Tohru - Origin 350 - 4xR16k 800 MHz - 4 GB RAM - 6.5.30 - on loan from Raion
Indy Gary - Indy - R5k 180 MHz - 24-bit XL Graphics -  192 MB RAM - 6.5.22
Mirrors
LarBob
Global Moderator
******

Posts: 89
Threads: 20
Joined: Dec 2017
Find Reply
06-03-2018, 06:53 PM
#5
Re: How to compile GCC 4.7.1 on IRIX
Ah, i didn't build it with gcc but mipspro. Just ignore getopt_long for now and try to build ppl without it.
dexter1
Global Moderator
******

Posts: 189
Threads: 10
Joined: May 2018
Find Reply
06-03-2018, 09:55 PM
#6
Re: How to compile GCC 4.7.1 on IRIX
<QUOTE author="dexter1" post_id="732" time="1528062954" user_id="141">
dexter1 post_id=732 time=1528062954 user_id=141 Wrote:Ah, i didn't build it with gcc but mipspro. Just ignore getopt_long for now and try to build ppl without it.

It's fine without it, although far from an ideal solution.

Octane Aezora - Octane - 2xR12k 400 MHz - V8 Graphics - 1216 MB RAM - 6.5.30
O2 Kiki - O2 - R5k 200 MHz - 128 MB RAM - 6.5.30
Two O350 modules Calcifer - Origin 300 - 4xR14k 500 MHz - 2 GB RAM - 6.5.30
Two O350 modules Tohru - Origin 350 - 4xR16k 800 MHz - 4 GB RAM - 6.5.30 - on loan from Raion
Indy Gary - Indy - R5k 180 MHz - 24-bit XL Graphics -  192 MB RAM - 6.5.22
Mirrors
LarBob
Global Moderator
******

Posts: 89
Threads: 20
Joined: Dec 2017
Find Reply
06-03-2018, 11:34 PM


Forum Jump:


Users browsing this thread: 1 Guest(s)