Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alien Build Plugin fails to in stall on AIX #410

Open
Jim19249124 opened this issue Apr 22, 2024 · 7 comments
Open

Alien Build Plugin fails to in stall on AIX #410

Jim19249124 opened this issue Apr 22, 2024 · 7 comments
Assignees

Comments

@Jim19249124
Copy link

Trying to install MSOffice::Word::Template and is failing due to issue with dependency Alien::Build::Plugin.

It appears the Setup.pm file does not account for architecture ppc-aix-thread-multi-64all.

Looking at Setup.pm there is code to find the number of cpus for aix but not include code for aix in the architecture verification routine.

I have 2 perl versions installed.
v28 is delivered by IBM as part of the OS. v38 was installed from IBM's Aix toolbox repository.
Note they build against different architecture strings..
I'm attempting to install against v38

This is perl 5, version 38, subversion 2 (v5.38.2) built for ppc-aix-thread-multi-64all
This is perl 5, version 28, subversion 1 (v5.28.1) built for aix-thread-multi

Thanks in advance for any assistance.

@plicease
Copy link
Member

plicease commented Apr 23, 2024

I assume Alien::Build is getting pulled in for Alien::Libxml2? Can you provide more details on the exact nature of the fail, and any diagnostics that are produced? The platform detection is supposed to fallback on unknown if it can't detect it

$arch->{name} = 'unknown';

but I don't have an AIX to test on. It will die if archname or ptrsize aren't set. We might want to warn on that and set to unknown instead. They should have a value though, so if that were the cause a lot of other stuff would also likely not work.

@plicease
Copy link
Member

// cc: @zmughal (who worked on the platform detection).

@Jim19249124
Copy link
Author

Jim19249124 commented Apr 23, 2024 via email

@plicease
Copy link
Member

I think this is the key diagnostic:

+ autopoint -f
autogen.sh[15]: autopoint:  not found.
external command failed at

libxml2 is provided in .tar.xz format, and I recently updated the Alien::xz to build the configure script for xz since it is no longer provided in the tarballs that we are getting. (if interested you can read the background here PerlAlien/Alien-xz#8). Unfortunately this pulls in a dependency we didn't have before on autopoint (PerlAlien/Alien-xz#11). My plan is to either avoid that dependency or alienize autopoint but I haven't been able to focus on that yet.

TL;DR: if you can install a system package of one of these:

  1. autopoint
  2. xz
  3. libxml2

It should unblock you.

@Jim19249124
Copy link
Author

Jim19249124 commented Apr 23, 2024 via email

@plicease
Copy link
Member

Gosh when I was using AIX at IBM 20 years ago we didn't have rpms :)

I think you are right I think autopoint comes from gettext. It may be easier to install xz or libxml2 instead. Be sure to install the dev packages, these usually come as separate packages on rpm based systems that I am familiar with.

I would love to fix the error with -a, but I don't have an AIX to test with. What I need is a recursive option, plus the appropriate options to preserve timestamp, permissions, ownership (where practical) and symlinks (as symlinks). I think from reading on line -Rp will do everything except symlink duplication. If you can help me figure that out and test a modified version of Alien-Build to confirm that change works I'd be grateful. The -H -L and -P option seem to modify the behavior with -R for symbolic links but I don't quite understand what they do from the description.

@Jim19249124
Copy link
Author

Jim19249124 commented Apr 24, 2024 via email

@plicease plicease self-assigned this Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants