Was going to edit the original post, but was easier to do a new one.

Went back to this again recently to make some better changes (did not mean to take two months… sigh) and it wouldn’t build! I’d either completely forgotten some of the steps I took last time or the build has changed a bit? Note that even though my changes are still on HammerDB 5.0 that doesn’t mean there haven’t been upstream changes - The HammerDB source code you obtain from Github is more like a “build system” as opposed to the actual source you are compiling. When you build from source you are actually running Tcl scripts that download source code from the TPC/HammerDB website and then it builds that.

Anyway, further to last time ended up doing this:

1. Turns out I did need to do this bit:

    sudo ln -s /usr/pkg/bin/python3.12-config /usr/pkg/bin/python3-config
   

2. Running a ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt update would fail because the Makefiles wanted to use -ldl which isn’t applicable for (Net)BSD. So instead I stepped through the process manually:
   1. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt extract.
   2. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt configure.
   3. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt compile.
   4. Which would then fail, but I could edit the relevant Makefile and remove the -ldl and re-run the compile and repeat this until all components had built.
   5. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt distribute.
   6. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt finalize. Weirdly, even though I’m sure these are the same steps update does, this didn’t copy all the required libraries into the distributions so I had one final step of:
   7. ./Build-Linux.sh x64 Setup/HammerDB-Linux.bawt update.

3. That got me working Dev builds again. I also had a play about withstrace/dtrace/ktrace on the Prod builds and figured out they were actually fine, it was just looking for the libraries in an odd place; Say I had extracted at /home/me/temp/HammerDB-5.0, well, it was looking for /home/me/temp/lib. So I just copied the lib folder from a Dev build to that location and then the Prod builds would run fine; I started with strace just for ease of use, but the version on NetBSD is old and doesn’t print full filepaths which makes it useless. ktrace and kdump are pretty easy to use as well, but only if you know what you are looking for upfront and I didn’t, whereas dtrace is more complex, but I could get it to put all filepaths for HammerDB and eyeball a non-existent one:

    syscall::stat:entry, syscall::lstat:entry, syscall::access:entry
    /execname == "hammerdb"/
    {
        self->path = copyinstr(arg0);
        self->probe = probefunc;
    }
    syscall::stat:return, syscall::lstat:return, syscall::access:return
    /execname == "hammerdb" && self->path != NULL/
    {
        printf("%d %s %s errno=%d\n", pid, self->probe, self->path, errno);
        self->path = 0;
    }
   

Next for me on this: Figuring out a better Makefile fix so that’s less tedious to do. And it might not be impossible to do a Pkgsrc package for this since the separate steps (extract, configure, etc) would align with Pkgsrc.

• Tags:
  • program

A follow-up to 75+75.

I started trying to ramp things up over my base of 75 minutes of running a week at the end of 2023 - I just thought it was sad to let go all those years of work building up my distance. And on and off I’ve managed to do it. I managed nine Brimmond Hill (24km) runs last year, plus one Bennachie (21km, but totalling around 27km with the runs to and from the bus to get there). This year I’ve managed three Brimmond and Elrick (30km) runs. None of that is possible with a limit of just 75 minutes running.

I still struggle for time for running, especially now the dog is so old and can’t really be left alone for more than three hours at a time, but I do want to try to keep my distance up a bit so I’m trying a new weekly base of:

• 225 minutes running
• 75 minutes of strength/yoga

Roughly working out as:

• Mon: 75 minutes of running
• Tue: 25 minutes of strength
• Wed: 75 minutes of running
• Thu: 25 minutes of strength
• Fri: 75 minutes of running
• Sat:
• Sun: 25 minutes of yoga

Although I could do with squeezing in the yoga in the week so it doesn’t interfere with weekends.

If I am lucky enough to find the time to fit in a long run (two to three hours) then all the better. But if need be I can also split the 75 minutes between mornings and evenings.

This actually only works out as 3% of my time - 75+75 was 1.5% - which still feels very reasonable and non-selfish to me, but it’s not my opinion that matters. Maybe one day I can have 3% of my wage as well, but that’s staying at 1.5% for the next couple of years at least.

My dog walking has rapidly decreased due to the age of the dog. She just can’t walk very far any more :-(. Doing more walks a day, just very short.

• Tags:
  • push

A brief review. I got this because, as I’ve said before, despite my best efforts to be restrained with my spending I’m not completely immune to consumerism and the pleasures of spending a (small) bit of my wage on myself: £26 on Vinted (although £30 with shipping and buyer protection).

• The top pocket is too small for a phone (very close to fitting my Pixel 7a), but I have got the older model which was released ten years ago so maybe there were smaller phones still knocking about then?
• There is a key clip in the top pocket which seems a bit pointless. I tried clipping my keys to it and they just rattled around. Maybe if your bag is full that wouldn’t happen? But I’ve just gone back to what I always do which is to take one key off my keyring and just take that single key with me when running.
• Fits one bag of Naturo 2kg dog food perfectly. Almost two, but not quite. It just (it was a squeeze, but I got it zipped up) fits 1x Harringtons 1.7kg dog food and 1x Purina Go-Cat 2kg cat food; So should fit 2x Harringtons dog food which is useful (to me)*.
• With a light load it really does lock into place, is comfortable and doesn’t move at all.
• With a heavier load (dog food) it did slide around slightly the first time I used it, but on a subsequent run I realised I could pull it tighter and lock it down (although it was then a little constrictive). Either way was better than trying to run with my none running bag though (also ten years old, but a 20L Case Logic not intended for running at all).
• I struggle to tighten the straps equally and this means one of the ladderlock buckles did start digging into my ribs once - they could do with a bit of padding under them - although it’s also easy to loosen and re-adjust.
• There is no way I can reach around to the side-pockets despite that being the intention - I think this is because it sits higher up on your back. I have to take it off to get to them.
• I should have probably got the 12L one for “running to the shops” runs, but that isn’t really why I got it - I got it for taking food and snacks for longer runs where my daily little 2L Kanken Hip Pack isn’t big enough (great for my phone and couple of butteries or my jacket, but not for a water bottle).
• I’ve used it on a 30k run for chucking my phone, jacket, water bottle and a little packed lunch in and there was plenty of room. Easily comfortable enough that you can forget you are wearing it.
• It comes in a nice bright pink!

* - Confirmed: Easily zips up with 2x 1.7kg bags.

• Tags:
  • push