donny wrote:In my experience, Nekoware and SGI Freeware work just fine together. I have the entire May '04 Freeware installed, and most of the neko beta packages. No probs at all on any of my boxes.
True. But what I'd really like to do is ditch the duplicates. I ain't got all that much disk space, and two copies each of a hunnerd and thirty-five shared libraries seems ... redundant ? Suggestions, anyone ? Links from /nekoware to /freeware should work ?
If you distribute your own packages please do not install them under /usr/freeware, or give them names beginning with "fw_". If you do it's likely to cause trouble if/when we eventually add it to our distribution.
What you can do is port software to IRIX and send any patches to the official maintainers (and to us).
dexter1 wrote:Linking libs from freeware to nekoware and vice-versa could very well work. I tried for instance Diego's GeneratriX and while he had only freeware prereqs, i 'set rulesoverride on' installed it and ran fine with nekoware libs.
dexter1 wrote: I agree with some of the criticism that having two software environment "flavors" kinda dilutes the effort. But please, also understand this from a historic point-of-view, written in the second paragraph.
hamei wrote:So .... are the libraries dependent on path order like on Intel, so if I first switched nekoware and freeware's order, I'd be getting neko libs rather than freeware libs ? Then could remove freeware directories from the path for further tests without upsetting the applecart ?
dexter1 wrote: Uhm, not really. There are several factors:
1) SGI versioning. SGI keeps it's version info in the ELF header of the .so library, while linux works with absolute file names and version numbering behind the .so suffix
If you want a specific version, you can do it either way:
The SGI way: set the version dependency to a specific SGI lib version in the linking stage:
The linux way: link to a specific filename/version:
Users browsing this forum: No registered users and 2 guests