FreeBSD Ports -> IRIX - Printable Version

+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Development/Porting (//forums.irixnet.org/forum-9.html)
+--- Thread: FreeBSD Ports -> IRIX (/thread-4011.html)

---

RE: FreeBSD Ports -> IRIX - Raion - 09-26-2023

jwhat, I highly suggest you require and use cURL. If you look at curl's documentation there is a way to set the certificate path, and it builds cleanly with both compilers. You can then include a bootstrap script that downloads a stable curl version, builds it with correct parameters, and then downloads the necessary certificate roots. wget = curl -O

---

RE: FreeBSD Ports -> IRIX - vishnu - 09-26-2023

(09-26-2023, 02:20 PM)Raion Wrote:  jwhat, I highly suggest you require and use cURL. If you look at curl's documentation there is a way to set the certificate path, and it builds cleanly with both compilers. You can then include a bootstrap script that downloads a stable curl version, builds it with correct parameters, and then downloads the necessary certificate roots. wget = curl -O

I'm a huge fan of the Lock Picking Lawyer's youtube channel, and as far as I can recall, I've never seen him fail to pick a lock, usually within seconds or at least a few minutes. On the other hand, computer security is a laughfest, check your logfiles every day and install each update on the day it's released. And I'm not talking about Windows, there no such thing as "Windows security."

---

RE: FreeBSD Ports -> IRIX - Raion - 09-26-2023

You're talking about my signature? That's not part of the message.

---

RE: FreeBSD Ports -> IRIX - jwhat - 09-28-2023

Hi Raion,

I have got "fetch-recursive" target to work for openssl using Nekoware curl (and its required depedendencies).
This requires turning off CHECKSUM:

# bmake -d l fetch-recursive EXTRACT_BEFORE_ARGS=-xzf CC=c99 CFLAGS="-64 -mips4 -O2" LDFLAGS="-64 -mips4" NO_CHECKSUM=yes prefix=/usr/local2

So one more gitlab issue closed, now back to see if I can get "build" target to work (could not build previously, as I could not get source to download).

Using Nekoware as part of bootstrap code seems like a reasonable choice, its its stable and does not require building more stuff.

Cheers from Oz,

jwhat/John.

---

RE: FreeBSD Ports -> IRIX - Raion - 09-28-2023

Ok. We will need to provide root certificates as well in order to prevent SSL errors.

We absolutely need to fix check sums long-term though.

---

RE: FreeBSD Ports -> IRIX - jwhat - 09-29-2023

HI Raion,

the CHECKSUM is using OpenSSL MD5 code, so need to bootstrap OpenSSL to get this.

Hence focus on OpenSSL as initial target, it is used for lots of things.

I have almost got "dialog4ports" to build.

It is using FreeBSD specific systems calls and other bits and pieces and so needed to create a BSD compatability library (libbsdports.a) with the missing functions.

Now advanced to point of getting unresolved functions on link, so need to add extra functions into libbsdports.a library.

So new gitlab issue for work required to add extra compatability functions...

If can get to building OpenSSL then would have working IRIX ports solution.

Cheers from Oz,

jwhat/John.

---

RE: FreeBSD Ports -> IRIX - Raion - 09-29-2023

We will also need mtree and others too. I will probably at some point try to take some time off and do a script that can also allow for "flavors" to be passed to the ports tree and thus we can build packages for say, nekoware or other packaging; or even potentially that RSE stuff if they wanted to collaborate/fork the work into their own project.

whenever I have time and access to a machine with your tree setup I'll just crank out ports and such, setup some pull requests and offer some suggestions on what categories to retain and what kinds of things can be "frozen" on versions and what can/should be synced/maintained.

---

RE: FreeBSD Ports -> IRIX - jwhat - 10-02-2023

Hi Raion,

I now have only only small number of unresolved functions on dialog4ports:



The problem is that I cannot find where these functions are defined, as I think dialog/ncurses is doing some #define or SED trickery to change the function names depending on whether you are building with WCHAR or not.

I changed the bootstrap script to use wide char as this is what current FreeBSD dialog4ports is using, but still get unresolved issue.

People are welcome to look at this, as I am a bit tired of it for the moment.

NOTE: All the ncursesw tests seem to work ok on IRIX with latest ncurses lib (6.4)

Cheers from Oz,

jwhat/John

---

RE: FreeBSD Ports -> IRIX - Raion - 10-02-2023

We don't have proper Unicode support so we should be turning that off.

---