This is really cool stuff - nice work Rick! If you want to do a writeup for
the OMP blog -we'd be happy to post ti!

There's an Ambitus project at OMP which might be an interesting place to
help drive some of this work; the team working on things like build
environment, upstreaming any code support, and generally ensuring s390x
support is maintained in a sustainable way.

Let me know what you think...

Thanks,

John


On Mon, Mar 30, 2020 at 10:46 AM Rick Troth <[email protected]> wrote:

> What did y'all do over this weekend while you were locked up?
> Geeky me noticed a half dozen packages in the Chicory collection which
> needed update.
>
> They needed update ... what "update" means for Chicory is to cobble-up a
> new makefile for each package, usually just bumping the release number
> from the previous makefile, and then driving a build for each platform
> of interest. These are just some packages for which there is a newer
> release of the source.
>
> Platform of interest ... for me that's always S390, but also I386 and ARM.
>
> What packages? I mentioned BINUTILS a few days ago. There are also the
> latest release of Python 3 and the final release of Python 2. But also
> TAR, TCSH, TEXINFO, WGET, and ZSH. (SUDO was on the list, but it works
> better in the core OS, not supplemental via Chicory.) The list looks
> like ...
>
>     tar-1.32
>     tcsh-6.22.02
>     texinfo-6.7
>     wget-1.20.3
>     zsh-5.8
>     python-3.8.2
>     python-2.7.17
>     binutils-2.34
>
>
> The first five are what I worked on this weekend.
> Chicory is great! Hardly any time at all to change a prior "wrapper
> makefile" for the new release. Wrapper makefile sits above the package
> source and drives Biggest time sink is making the build behave. (My
> build farm is very much a hobby thing, so it's scattered.)
>
> I build them statically when possible. If something goes wrong with the
> static build, the build can be re-driven using dynamic linkage. (Dynamic
> has advantages, but drives co-reqs, sometimes broadly.) Once they're
> built, they can be installed easily using the crude Chicory scripts. (A
> collection of shell scripts which will only improve as they get used.)
> And one can always cook the recipe manually.
>
>     *rsync://chic.casita.net/opt/*/package/*/Linux-s390x/*
>
>
> As I write this note, I see that some of the packages still lack S390X.
> Sorry about that. Will go back and re-try them.
>
> -- R; <><
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to