Skip Menu |

This queue is for tickets about the Alien-LibXML CPAN distribution.

Report information
The Basics
Id: 132130
Status: open
Priority: 0/
Queue: Alien-LibXML

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.004
Fixed in: (no value)



Subject: t/01-compiler.t fails on darwin
Here's the test output --- seems to happen regardless of the perl version (tried 5.28.0 ... 5.31.9): ... Output from './Build test': Testing library (if applicable) ... Done + pkg-config --modversion libxml-2.0 t/00-use.t ....... ok # COMPILER: /usr/bin/cc # CFLAGS: -I/usr/include/libxml2 # LIBS: -lxml2 # OUTPUT: t/tree1.exe # INPUT: t/tree1.c t/tree1.c:13:10: fatal error: 'libxml/parser.h' file not found #include <libxml/parser.h> ^~~~~~~~~~~~~~~~~ 1 error generated. # Failed test at t/01-compiler.t line 52. Can't exec "t/tree1.exe": No such file or directory at t/01-compiler.t line 55. # Failed test at t/01-compiler.t line 55. # got: undef # expected: 'node type: Element, name: root # node type: Element, name: inner # ' # Looks like you failed 2 tests of 2. t/01-compiler.t .. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/2 subtests ...
I don't have a Mac to test this on. And non-Mac-OS distributions of Darwin are basically nonexistent these days. I'd happily accept a patch to fix it though.
On 2020-03-18 06:19:01, TOBYINK wrote: Show quoted text
> I don't have a Mac to test this on. And non-Mac-OS distributions of > Darwin are basically nonexistent these days. > > I'd happily accept a patch to fix it though.
Some research: $ pkg-config --cflags libxml-2.0 -I/usr/include/libxml2 -> But this directory did not exist at all, in fact, there were no include directories or files here. But I found a helpful page: https://silvae86.github.io/sysadmin/mac/osx/mojave/beta/libxml2/2018/07/05/fixing-missing-headers-for-homebrew-in-mac-osx-mojave/ After running the proposed "installer" command the include files were installed --- and the build of Alien-LibXML was successful. So probably there's not much what the Alien-LibXML can do here, other than checking if the directory in the -I option actually exists, and pointing the user to the possible solution.