Some compilation info
#21
Re: Some compilation info
dexter1 post_id=2052 time=1533555984 user_id=141 Wrote:The symbol '__sgi' (not '__sgi__') is defined when compiling c code under IRIX. I'm not sure if gcc will set that define
Yes, GCC does define it too. It's my preferred way of identifying IRIX-specific code.

gijoe77 post_id=2053 time=1533559067 user_id=243 Wrote:so lets say I have "__sig__" in my code, can i "trigger" this code by doing a "-D__sgi__" in CPPFLAGS?
Yes. (Once you correct the small typo!) But if you use __sgi, you don't need to add anything to CPPFLAGS, since that's predefined by both of the commonly used compilers. (And, IIRC, the __ prefix is supposed to be reserved for use by compiler vendors, and not used in user-written code according to the C standards.)

gijoe77 post_id=2053 time=1533559067 user_id=243 Wrote:Are there certain "-D" strings you use for porting stuff to IRIX? my notes from long ago have "-DIP32 -DIRIX" but I figure those are not very helpful in most software packages
Well, it looks to me like __sgi was intended to be used for that purpose. But plenty of packages will have their own ideas about what to define to identify different OSes. My recommendation is to use __sgi for code you write. For third-party code you work with, don't expect any sort of standardization at all.

SGI:  Indigo, Indigo2, Octane, Origin 300
Sun:  SPARCstation 20, Ultra 2, Blade 2500, T5240
HP:  9000/380, 425e, C8000
Digital: DECstation 5000/125
jpstewart
Octane

Posts: 54
Threads: 0
Joined: May 2018
Find Reply
08-06-2018, 03:09 PM
#22
Re: Some compilation info
Here are my notes on compiling gftp version 2.0.19 (Nekoware's version is 2.0.17)
edit: I looked this over again because I realized I compiled originally with R10k o2 optimizations, so I dug a little deeper into it for the Tezro optimizations. Certain CFLAGS and CPPFLAGS seem to break compilation

Show ContentSpoiler:
gijoe77
Tezro

Posts: 469
Threads: 28
Joined: Jun 2018
Find Reply
08-07-2018, 01:43 PM
#23
Re: Some compilation info
My failed attempt at compiling Filezilla 3.35.1 - GCC 4.7.3 is apparently unable to compile it also... I guess we need a newer GCC...

Show ContentSpoiler:
gijoe77
Tezro

Posts: 469
Threads: 28
Joined: Jun 2018
Find Reply
08-07-2018, 01:47 PM
#24
Re: Some compilation info
gijoe77 post_id=2084 time=1533649626 user_id=243 Wrote:My failed attempt at compiling Filezilla 3.35.1 - GCC 4.7.3 is apparently unable to compile it also... I guess we need a newer GCC...

Show ContentSpoiler:

Not happening any time soon. IRIX ABI support was removed in GCCs after 4.7.x. IRIX headers also definitely do not support C++14, haha. Also, weird that it requires C++14. FileZilla isn't great anyway I guess. Tongue

Octane Aezora - Octane - 2xR10k 250 MHz - SI Graphics - 1 GB 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: 69
Threads: 14
Joined: Dec 2017
Find Reply
08-10-2018, 05:23 AM
#25
Re: Some compilation info
LarBob post_id=2163 time=1533878620 user_id=70 Wrote:Not happening any time soon. IRIX ABI support was removed in GCCs after 4.7.x. IRIX headers also definitely do not support C++14, haha. Also, weird that it requires C++14. FileZilla isn't great anyway I guess. Tongue

oh that's pretty crappy, thanks for the info - good to know.
gijoe77
Tezro

Posts: 469
Threads: 28
Joined: Jun 2018
Find Reply
08-10-2018, 03:51 PM


Forum Jump:


Users browsing this thread: 1 Guest(s)