php / php/pecl-mail-mailparse

Cannot build 3.1.6

Open
#35 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
C
Stars
38
Forks
35
PR merge metrics
No merged PRs in 30d

Description

TL;DR: I tried to build mailparse-3.1.6 however it fails with #error The mailparse extension requires the mbstring extension!

system: Debian GNU/Linux 12 (bookworm)
php: PHP 8.2.7 (cli) (built: Jun 9 2023 19:37:27) (NTS)

  • extraction: ok
  • phpize: ok
Configuring for:
PHP Api Version:         20220829
Zend Module Api No:      20220829
Zend Extension Api No:   420220829
configure.ac:165: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:165: You should run autoupdate.
build/libtool.m4:100: AC_PROG_LIBTOOL is expanded from...
configure.ac:165: the top level
  • configure: ok
checking libmbfl headers... found in /usr/include/php/20220829/ext/mbstring
  • make: error

I think the issue is because "HAVE_MBSTRING" is not set.

Adding #define HAVE_MBSTRING 1 into the generated config.h file makes everything compile correctly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with configure.ac and the generated config.h, then reproduce the make failure using the reported Debian 12 and PHP 8.2 setup. Check how the mbstring headers are detected and whether HAVE_MBSTRING is propagated. Done means mailparse-3.1.6 builds without manually editing config.h.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.