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
Debian and aircrack-ng build failures #2547
Comments
What are the results with current git? |
I cannot test on the Debian porter boxes because I don't have access to them. I tested the tip of Master (608d321) on my PowerMac G5 (with Altivec) and passed all tests. When I checked out the 1.7 tag, I experienced failures. So I would say you fixed it on Master. Thank you very much, sir! Looking at the check-ins from May 11 (tag 1.7) until today (Master), I don't see something that looks like it affected your actual source code. It looks like they were script cleanups from Shellcheck findings. (Assuming I am parsing The next question is, is there a check-in that I can alert the Debian maintainer to pick-up? Or should they just use a diff from 1.7 (2cdfba4) until today (608d321)? Or maybe something else? Thanks in advance. A patch from 1.7 (2cdfba4) until today (608d321) looks like it will be a big patch. But what the heck. If it fixes the problem, then so be it.
And
|
I'm thinking out loud... Would a diff of the following files from 1.7 to Master provide what Debian needs?
|
Ping @glaubitz. |
You should request access to the GCC Compile Farm [1]. There you can access Linux, BSD and Solars machines running on various hardware. There are PowerPC machines available for running such tests. |
++. The Compile Farm is very useful. Do you know the specs on Debian's porter box? Does it align with one of the machines available on the CFarm? I think CFarm provides POWER7, POWER8, POWER9 and POWER10. POWER10 was announced this week. I'm not aware of Altivec-only (PowerMac G5's) or non-Altivec (PowerMac G4's or G3's?) |
Testsuite still fails:
And it looks like that the reason for the failure is the unconditional use of POWER8 instructions despite the target using an older POWER baseline. I haven't found a configure option yet to disable POWER8 instructions. |
Defect Report
Issue type
make check
issue - Attachconfig.log
and provide relevant system information such aslscpu
- Make sure dependencies are installedSystem information
Debian Sid, which is Unstable. Packages enter Unstable, then move to Testing, then move to Release.
Aircrack-ng version
Airmon-ng debug information
I don't think this is related to airmon-ng, but I might be mistaken.
Defect
Details
It looks like aircrack-ng has several build failures on Debian. See https://buildd.debian.org/status/package.php?p=aircrack-ng&suite=sid . The failures are shown in red and labeled "Build Attempted." Clicking the Build Attempted link shows where the build failed.
The output of
make test
ormake check
is shown below for ppc64. I don't have access to the box, so I don't have access to some of the log files.If I am parsing output from PPC64 correctly, then this was the configure line used.
--with-gcrypt
looks interesting.How to reproduce the issue
The Debian build results show how Debian is building the package. See https://buildd.debian.org/status/package.php?p=aircrack-ng&suite=sid .
I have an old PowerMac G5 with Altivec. I can provide access to the machine if desired. I am also available to help with troubleshooting. I have a C/C++ background, and I have experience porting to various architectures like PPC and PPC64.
Related issues
I think these may be related issues, but I am not certain:
The text was updated successfully, but these errors were encountered: