Re: WARNING: exim 4.99 Fedora current build disfunctional

Andrew C Aitchison via Exim-users <[email protected]> Mon, 17 Nov 2025 16:00:48 +0000 (GMT)
Newsgroups gmane.mail.exim.user
Message-ID <[email protected]>
On Mon, 17 Nov 2025, Cyborg via Exim-users wrote:

> Am 17.11.25 um 15:24 schrieb Jeremy Harris via Exim-users:
>> On 2025/11/17 1:38 PM, Tim Jackson via Exim-users wrote:
>>> Is it possible that this originates in the Exim upstream itself? I'm not 
>>> very familiar with the whole Exim build system, and haven't tried building 
>>> 4.99 myself but at a casual glance, module loading and drtables.c has had 
>>> a revamp and seems to now try to dlopen() a file named 
>>> "<modname>_lookup.so" for lookups (e.g. mysql_lookup.so), which is new, 
>>> but lookups/Makefile still 
>>> refers to (for example) mysql.so. Maybe I'm misunderstanding though.
>> 
>> Nope.  The project build sequence results in "<modname>_lookup.so"  *in a 
>> different directory*
>> (along with .so files for any routers, transports, authenticators and other 
>> misc components
>> which the build config has been set to build as loadbable modules.
>> 
>> The file <modname>.so is a precursor, and they should not have been trying 
>> to use it.
>> 
>> I think this is a mistake in the Fedora package build.  However, it is a 
>> step not well
>> detailed in Exim's documentation so I've added a bit of descriptions in 
>> EDITME file (which
>> becomes a makefile).
>> 
> in case anyone else wants to auto test for such an issue, a have made a 
> minimal config for a testcase:
>
> You need a working database, but you don't need a sql setup in that db except 
> a valid login.
> You DO NOT need a running exim to have that testcase working.
>
> exim.conf:
>
> #
> # minimum test config for db access
> #
>
> primary_hostname = testfarm.yourproject.edu
>
> keep_environment = PATH
>
> message_logs                        = false
>
> hide mysql_servers = localhost/<DBNANE>/<DBUSER>/<DBPASSWORD>
>
> /exim.conf
>
> a working example:
>
> # exim -be '${lookup mysql {SELECT 1}}'
> 1
>
> a none working example:
>
> # exim -be '${lookup mysql {SELECT * from mail_config LIMIT 1}}'
> Failed: unknown lookup type "mysql"

Do you think you can turn that into a patch for the exim test suite
- instructions at Exim/exim/test/README.
I can help, or I could do it but I don't have Fedora to test the test :-)

-- 
Andrew C. Aitchison                      Kendal, UK
                    [email protected]

-- 
## subscription configuration (requires account):
##   https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
##   [email protected]
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/