Re: [exim] 4.94.2+taintwarn branch failing to compile

2021-05-14 Thread Paul Griffith via Exim-users

-- Original Message --
From: "Heiko Schlittermann via Exim-users" 
To: "exim-users@exim.org" 
Sent: 5/14/2021 1:41:34 AM
Subject: Re: [exim] 4.94.2+taintwarn branch failing to compile

>Paul Griffith via Exim-users  (Do 13 Mai 2021 18:33:54 
>CEST):
>>
>>
>>  -- Original Message --
>>  >Paul
>>
>>  I am able to go into the build directory and  run "make exim" and the
>>  exim binary is able to be compiled.
>
>You are not expected to chdir into the build directory. You are expected
>to be *above* the build directory.
>

Heiko,

Thank you for responding,

I was only in the build directory to troubleshoot why the build was 
failing on my system. Normally I don't have any trouble with Exim.


>
> heiko@x1:…/src $ ls
> LICENSE Local Makefile build-… src …
>
>And, additionally try a "make distclean" before doing anything else.
>(This will let your Local/Makefile* inplace. So, no pain is expected.)
>
>>  build-Linux-x86_64]# make exim_fixdb
>…
>
>Again, first, you're not expected to sit in the build* directory, and
>2nd, you're not expected to "make …" each tool individually.
>
This was just part of my troubleshooting step to pin point the trouble 
point on my system.

>
>I can't reproduce your issue. but this:
>
>>/cs/local/bin/ld: exim_fixdb.o: in function `is_tainted2':
>>exim_dbutil.c:(.text+0x178): undefined reference to
>>  `allow_insecure_tainted_data'
>>collect2: error: ld returned 1 exit status
>>make: *** [Makefile:655: exim_fixdb] Error 1
>
>reads as if somewhere an outdated *.a is hanging around. (or a broken
>compile cache?)
>

Thank you for the hints, I will look along that line.

I was able to get a complete compile without the "undefined reference" 
error by adding macro-globals.o to the lines OBJ_DUMPDB, OBJ_FIXDB and 
OBJ_TIDYDB in OS/Makefile-Base.

Since I am the only one who is having this problem, the issue appears to 
be local to me.

Best regards,
Paul

>
> Best regards from Dresden/Germany
> Viele Grüße aus Dresden
> Heiko Schlittermann
>--
>  SCHLITTERMANN.de  internet & unix support -
>  Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
>  gnupg encrypted messages are welcome --- key ID: F69376CE -
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


Re: [exim] 4.94.2+taintwarn branch failing to compile

2021-05-14 Thread Heiko Schlittermann via Exim-users
Paul Griffith via Exim-users  (Do 13 Mai 2021 18:33:54 
CEST):
> 
> 
> -- Original Message --
> >Paul
> 
> I am able to go into the build directory and  run "make exim" and the 
> exim binary is able to be compiled.

You are not expected to chdir into the build directory. You are expected
to be *above* the build directory.

heiko@x1:…/src $ ls
LICENSE Local Makefile build-… src …

And, additionally try a "make distclean" before doing anything else.
(This will let your Local/Makefile* inplace. So, no pain is expected.)

> build-Linux-x86_64]# make exim_fixdb
…

Again, first, you're not expected to sit in the build* directory, and
2nd, you're not expected to "make …" each tool individually.

I can't reproduce your issue. but this:

>   /cs/local/bin/ld: exim_fixdb.o: in function `is_tainted2':
>   exim_dbutil.c:(.text+0x178): undefined reference to 
> `allow_insecure_tainted_data'
>   collect2: error: ld returned 1 exit status
>   make: *** [Makefile:655: exim_fixdb] Error 1

reads as if somewhere an outdated *.a is hanging around. (or a broken
compile cache?)

Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
 SCHLITTERMANN.de  internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --- key ID: F69376CE -


signature.asc
Description: PGP signature
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


Re: [exim] 4.94.2+taintwarn branch failing to compile

2021-05-13 Thread Paul Griffith via Exim-users



-- Original Message --
From: "Paul Griffith" 
To: "exim-users@exim.org" 
Sent: 5/13/2021 10:38:38 AM
Subject:  4.94.2+taintwarn branch failing to comile

>Hello,
>
>I am compiling Exim 4.94.2+taintwarn branch and it is failing with a
>compile error (below). I am able to compile 4.94.2 without any issues,
>but then again it doesn't have the taintwarn patch. That was my little
>test to ensure my build environment is working.
>
>
>I haven't see any other user run into this issue on the mailing list. I
>am running CentOS 7.9, I downloaded this branch just a few days ago.
>
>...snip...
>cc exim_dbmbuild.c
>cc -o exim_dbmbuild
>  >>> exim_dbmbuild utility built
>
>cc -DEXIM_DUMPDB exim_dbutil.c
>cc -DCOMPILE_UTILITY os.c
>cc -DCOMPILE_UTILITY store.c
>cc -o exim_dumpdb
>/cs/local/bin/ld: exim_dumpdb.o: in function `is_tainted2':
>exim_dbutil.c:(.text+0x1a4): undefined reference to
>`allow_insecure_tainted_data'
>collect2: error: ld returned 1 exit status
>make[1]: *** [Makefile:640: exim_dumpdb] Error 1
>make[1]: Leaving directory
>'/tmp/xsys.28373.0/exim-4.94.2-taintwarn/build-Linux-x86_64'
>make: *** [Makefile:35: all] Error 2
>[ exim-4.94.2-taintwarn]#
>
>...snip
>
>grep  ALLOW_INSECURE_TAINTED_DATA Local/Makefile
># "allow_insecure_tainted_data" to turn taint failures into warnings.
>ALLOW_INSECURE_TAINTED_DATA=yes
>
>exim-4.94.2-taintwarn]# cc --version
>cc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
>Copyright (C) 2015 Free Software Foundation, Inc.
>This is free software; see the source for copying conditions.  There is
>NO
>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>PURPOSE.
>
>
>
>Any hints
>
>Thank you
>Paul

I am able to go into the build directory and  run "make exim" and the 
exim binary is able to be compiled.
  build-Linux-x86_64]# make exim
  /bin/sh ../scripts/Configure-config.h "make"
  make[1]: Entering directory 
'/tmp/xsys.28373.0/exim-4.94.2-taintwarn/build-Linux-x86_64'
  make[1]: 'buildconfig' is up to date.
  make[1]: Leaving directory 
'/tmp/xsys.28373.0/exim-4.94.2-taintwarn/build-Linux-x86_64'
  Building configuration file config.h
  >>> config.h built
  ... snip...
cc -o exim

  >>> exim binary built
  Now, if I run "make utils", it fails, I am going to poke around the 
Makefile and  to see what I find.
  build-Linux-x86_64]# make utils
 >>> exicyclog script built
  >>> exinext script built
  >>> exiwhat script built
  >>> exigrep script built
  >>> eximstats script built
  >>> exipick script built
  >>> exiqgrep script built
  >>> exiqsumm script built
  >>> transport-filter.pl script built
  >>> convert4r3 script built
  >>> convert4r4 script built
  >>> exim_checkaccess script built
  cc exim_dbmbuild.c
  cc -o exim_dbmbuild
  >>> exim_dbmbuild utility built
  cc -DEXIM_DUMPDB exim_dbutil.c
  cc -DCOMPILE_UTILITY os.c
  cc -DCOMPILE_UTILITY store.c
  cc -o exim_dumpdb
  /cs/local/bin/ld: exim_dumpdb.o: in function `is_tainted2':
  exim_dbutil.c:(.text+0x1a4): undefined reference to 
`allow_insecure_tainted_data'
  collect2: error: ld returned 1 exit status
  make: *** [Makefile:640: exim_dumpdb] Error 1
Other utils are also failing.
build-Linux-x86_64]# make exim_fixdb
  cc -DEXIM_FIXDB exim_dbutil.c
  cc -DCOMPILE_UTILITY queue.c
  cc -o exim_fixdb
  /cs/local/bin/ld: exim_fixdb.o: in function `is_tainted2':
  exim_dbutil.c:(.text+0x178): undefined reference to 
`allow_insecure_tainted_data'
  collect2: error: ld returned 1 exit status
  make: *** [Makefile:655: exim_fixdb] Error 1
  [paulg@jazzy build-Linux-x86_64]# make exim_tidydb
  cc -DEXIM_TIDYDB exim_dbutil.c
  cc -o exim_tidydb
  /cs/local/bin/ld: exim_tidydb.o: in function `is_tainted2':
  exim_dbutil.c:(.text+0x1a4): undefined reference to 
`allow_insecure_tainted_data'
  collect2: error: ld returned 1 exit status
  make: *** [Makefile:670: exim_tidydb] Error 1
  [paulg@jazzy build-Linux-x86_64]# make exim_lock
  cc exim_lock.c
  cc -o exim_lock
  >>> exim_lock utility built
Am I the only seeing this problem?
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/