groovy2shoes has quit [Read error: Connection reset by peer]
groovy2shoes has joined #crux
tarxvfz has quit [Ping timeout: 256 seconds]
tarxvfz has joined #crux
tarxvfz has quit [Quit: tarxvfz]
cruxfan69 has quit [Ping timeout: 264 seconds]
cruxfan69 has joined #crux
joe9 has quit [Quit: leaving]
dlcusa has joined #crux
<dlcusa>
If you're curious why IBM mainframes still sell, Dave Plumber explains it extremely densely at https://www.youtube.com/watch?v=ouAG4vXFORc -- if you're an IT pro, you should know this.
<SiFuh>
r0ni: Yep, thinking of installing BeOS to avoid them
SiFuh_ has joined #crux
SiFuh has quit [Ping timeout: 246 seconds]
<dim44>
I'm cross compiling some ports. Why does prt-get install try to rebuild them when I transfer them over to the target machine? It works fine with pkgmk
<dim44>
*pkgadd
<SiFuh_>
prt-get/pkgadd* or pkgmk/pkgadd* ?
<dim44>
pkgmk/pkgadd
<dim44>
prt-get always tries to rebuild, pkgadd works
<SiFuh_>
Using -f with prt-get?
<dim44>
Nope, nothing, just tried with -is, same think
<dim44>
for instance: prt-get -is install jsoncpp-cross
<SiFuh_>
location of ports, work, distfiles (If using) changed?
<dim44>
hmmm, let me check
<SiFuh_>
Are you cross compiling (Different hardware) or just compiling for another machine that maybe slower?
<dim44>
Different hardware x86_64 to aarch64
<SiFuh_>
Got it
<dim44>
location is /usr/ports/crossLocal and is added to prt-get.conf. The output of prt-get info myCrossPort is correct
<dim44>
WORK is not set in either system, the only diff I found was PKGMK_IGNORE_NEW
<dim44>
I'm not sure what distfiles are
<SiFuh_>
distfiles and packages are set for where you download archives and where your prebuilt port rests. If you don't know about it or use it, then chances are you can skip that part
<SiFuh_>
By default they will be in the /usr/ports/<repo>/<port>/ directory
lavaball has quit [Remote host closed the connection]
<SiFuh_>
As far as I know, prt-get will not rebuild a port unless it is missing the final completed port tarball that was built or some flags were used
<dim44>
All the pkgmk.conf options (excluding flags needed for the compilation are the same). And the built packages go into the same folder.
<r0ni>
SiFuh_ I sadly remember very little about BeOS except I never got sound going but I could play nintendo roms on it lol
<dim44>
Btw it works fine with ports build on the target(aarch64) machine. Prt-get can remove and reinstall ports without rebuilding.
<dim44>
Okay I'll just let it do the rebuild and compare filenames and hashes
<SiFuh_>
r0ni: It's closed source now. Haiku is the replacement. I was just perusing it awhile ago. I plan to test it out. I was kind of impressed at their ports. Not impressed that everything runs as a super user though.
<SiFuh_>
But still, nice to see an OpenSource version of BeOS is still alive today.
<SiFuh_>
dim44: and compare locations, sizes and filenames and everything else that may be different
<ukky>
dim44: imho, you have to separate host /var/lib/pkg/db and your cross-target. I have not implemented cross-compiling yet, but that's how I would do it. You have to separate package directory too.
<r0ni>
ya i did like it, but ultimately I went back to linux. as there just wasn't any software
<SiFuh_>
r0ni: I swiftly went the repo for torrent, mutt, cmus, telegram, irssi, and so on and found most available
<dim44>
ukky: they are separate, I just go into the port folder on the build machine, execute a modifed pkgmk command and then rsync the whole folder over to the target
<SiFuh_>
r0ni: I plan to install it this week on the Beelink box and see how it peforms
<SiFuh_>
r0ni: I always liked OpenSolaris (Back in the day). Not a fan of OpenIndiana though
<ukky>
dim44: could it be that your aarch64 has different config and prt-get cannot find pre-built port files?
<SiFuh_>
ukky: This is what I was thinking but he says the configurations are almost identical. My only thought was maybe they are not being transferred over to the correct directories. Or the version numbers are different
<dim44>
ukky: It saves it's own built packages where it should
<dim44>
But I think I found a quite big difference
<dim44>
I was building the packages as user, and even though I change persmissions after copying
<dim44>
The .footprint has the build machine permissions
<SiFuh_>
Ahh
<ukky>
dim44: are you packaging files as non-0 user?
<dim44>
yeah, yeah, I should have been using fakeroot, but I haven't set it up yet
<ukky>
dim44: pkgadd will install files on your aarch64 system with UID/GID of your user on X86 system
<dim44>
it did, I hadn't noticed the user permissions. It doesn't help I use the same username for both systems.
<ukky>
the question remains: why prt-get make decision to rebuild package... I would do strace
<SiFuh_>
Because something has changed in what it expects. Such as permissions
lavaball has joined #crux
<ukky>
dim44: what is the output of this command on both of your systems: echo "$(id -u):$(id -g)"
<dim44>
'_' it was the packaging pkgmk.conf option. Took it for granted because I hadn't changed it from pkgmk-cross.conf
<dim44>
Btw, should I publish the ports? People doing this sort of thing might find it helpfull. I was thinking of just putting them on github
<ukky>
dim44: I can only speak for myself. I am interested in cross-compiling, but I need to develop my own workflow that will fit my vision how this should be intergated with CRUX environment. I can take inspiration from your work, though.
lavaball has quit [Remote host closed the connection]