[Raion]

> Raion - if you have an already compiling version of dialog4ports then I could use this to generate a patch file.

I don't handy, but it's something I can look into

[jwhat]

Hi Raion,

that would be very helpful, as I can then focus on getting patch mechanism going.

As you said in first discussion, “need dialog4ports” ;-)

There is bug in the dependency list creation and patching, so having useful example to work with would be great.

EDIT #1:
- Turns out that dialog4ports is dependent on "dialog" : https://invisible-island.net/dialog/#documentation
- Like bmake this is part of BSD base so needs to be part of bootstrap set of software

EDIT #2:
- I have added "dialog" into "/usr/ports/IRIX/bootstrap/irix-ports-bootstrap.sh” script so it can be installed to support building of "dialog4ports"
- As the official repo, only serves this up via https, I put in flags to allow copy from local archive (ie manually store *.tar.gz files and pick them up from there) and to control what gets built


Cheers from Oz,

jwhat/John

[jwhat]

Hi IRIX'ers,

I have not given up yet... but had crash on my development box, which took a week to clean up.

I believe that I now have the dependency resolution working (Mk/Scripts/irix.depends-list.sh) as when I go to to "fetch-recursive" from "/usr/ports/security/openssl" it goes up the tree and then fails in "pkg" target, when doing a compiler check: "/usr/ports/Mk/Uses/compiler.mk".

This make script pretty much assumes you have gcc as compiler and so fails with MIPSpro.

the Script is pretty horrible as it does lots of test on compiler coverage and it is not clear how this is then used later.

Raion - did you reach this point ?

I have started to look into it, to make it work with MIPSpro but it is pretty opaque...

Raised Issue in gitlab: https://gitlab.com/zebity/freebsd-ports/-/issues/10

So as you can see just trying to plug each hole as I work to get openssl built via Ports.

EDIT/DANGER !! : In hacking the "Uses/compiler.mk" script (which sends compiler output to /dev/null), I noticed that this does chmod on /dev/null which in turn breaks "Infosearch" (it errors with message saying it cannot find the page). So you need to chmod /dev/null back to a+wr to fix the created problem. This took me a day to diagnose and fix ....

Cheers from Oz,


jwhat/John.

[Raion]

Have had ZERO time with locksmithing school to work on this. But I'll give it a whirl and check through it soon.

[Raion]

I'm looking at this now and I'm really impressed at how far you have gotten. Haven't really booted it up yet as I need to rearrange my office yet again as I no longer have a space for my silicon graphics machines, but I will see if I can talk with some people who can offer me remote access and start working on this so that I'm not delaying any further.

Jwhat, what are the big to do list items that you think I could help with? At this point I'm really willing to let you handle the basics and I will only offer input where I think it's necessary. My view at this point is that we should just try to get things working with the tools that we already have and we can discuss packaging and bootstrapping a consistent environment after we have the actual ports tree functioning on some level.

My only area that I retain some hesitance on is the use of the default shells on IRIX due to known issues with their syntatical differences. Using something like mksh would enable us to get around some of those potential issues but I'm willing to table that for the time being.

[jwhat]

Hi Raion,

really there are no "big issues" its just a matter of plugging away on the various scripts and trying to understand what they are doing and why its not working.

So its an exercise in persistence really.

As you can see I added wrappers around major IRIX divergences, the one that is likely to be a bit of trouble will be to make pkg wrapper use IRIX inst.

This would be really good as it means that the SW installed would show up in swmgr / inst just like any other regular IRIX packaged software.

I have taken a bit of break on it at the moment, as have lots of work things to complete and got side tracked on IRIX man pages after I broke infosearch (again).

Cheers from Oz,


jwhat/John.

[Raion]

So that's actually doable (getting ports to build tardists)

How do you do it? Build the software normally, then stage it in a test directory, build a spec/idb file, then the script reconfigures/rebuilds software and installs to the proper prefix. We can ship the finished "ports" with spec/idb files already, but yeah, you can ship special hooks.

[jwhat]

Hi Raion,

is "How do you do it?" a rhetorical question ?

If so I think you and I are on aligned, just do the build into staging area and then automatically generate the spec/idb file.

The dependencies of the package should match the dependencies from the FreeBSD port tree.

That is my high level view at this point, but right now I have not managed to get to complete build :-(

Cheers from Oz,


jwhat/John

[jwhat]

Hi Raion,

I got distracted with getting IRIX man pages available ...

I spent $$ on buying old Bolsky/Korn "Korn" & "New Korn"  shell books and also in getting Man page up and running have been reading details of the sh man page.

I found this at bottom of sh man page on "Compatibility"

Code:

"When the shell is invoked as "sh", the following features are performed
    only when the current value of the _XPG variable is equal to 1 (one):

          - command substitution of the form "$( command )"
          - arithmetic expression of the form "$(( expression ))"
          - tilde expansion of pathnames
          - unsetting variables, not previously set or null, returns 0"

So as a lot of update I did related to changing the $() to back quotes ``, I think I will download new fork and use this to to create updated version build with the right _XPG env setting and see if this allow of less revisions.

It is always quicker the second time ;-) and I have much better understanding of how the scripts work. If I can avoid having to "fix" all the backquotes then job will be much easier.

Cheers from Oz,


jwhat

[jwhat]

Hi Raion & others,

I know you (Raion) are busy with career change.

I have some good news, having not touched this "project" for over a month.

I reverted most the the $( ) ==> ` ` (backquote) changes (only took around an hour) and tested with _XPG=1 env variable set.

It worked like a breeze!

I tested with recursive fetch of openssl and this went and tried to download files, but due to wget not supporting SSL still it failed.

As the back quote changes were by far the largest set of changes I makes, by avoiding these, I avoid all the debugging of these changes.

I have checked in updated scripts with the reverted code, so things are looking like this might be possible again...

Cheers from Oz,

jwhat/John.