Re: Link problems

From: Alessandro Vesely <vesely_at_tana.it>
Date: Sun, 01 Aug 2010 14:11:59 +0200

Hi Zenon,

On 31/Jul/10 17:01, Zenon Panoussis wrote:
> I built opendkim (as an rpm, but I don't think that in itself matters)
> and then built zdkimfilter against it. Here's what happens when
> zdkimfilter is invoked:
>
> zdkimfilter[7040]: started child
> zdkimfilter[7040]:id=00038367.4C54186A.00001B7F: signing for
> oracle_at_provocation.net with domain provocation.net, selector ubinas
> zdkimfilter[7040]:id=00038367.4C54186A.00001B7F: response: 250 Ok.

That's logged by courierlogger, capturing stderr output by zdkimfilter.

> courierfilter: profiling:/usr/src/redhat:Cannot create directory
> courierfilter:
> profiling:/usr/src/redhat/BUILD/opendkim-2.1.3/libopendkim/.libs/libopendkim_la-base64.gcda:Skip
>
> courierfilter: profiling:/usr/src/redhat:Cannot create directory
> courierfilter:
> profiling:/usr/src/redhat/BUILD/opendkim-2.1.3/libopendkim/.libs/libopendkim_la-dkim-cache.gcda:Skip

That is logged by gcc's instrumentation code for coverage tests. The
"mail" user lacks permissions to create the relevant directories for
saving coverage data, otherwise it would create them anew. See, e.g.,
http://gcc.gnu.org/onlinedocs/gcc-4.0.4/gcc/Gcov-Data-Files.html#Gcov-Data-Files

> and so on, and so forth.
>
> ldd on zdkimfilter, opendkim, libopendkim.so.2 etc shows correct
> paths to /lib or /usr/lib for everything.
>
> I saved the compile output. If I grep in it for libopendkim_la-base64,
> I see nothing suspicious:
>
> /bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99
> -DHAVE_CONFIG_H -I. -I.. -I/usr/kerberos/include -I/usr/include
> -pthread -g -fprofile-arcs -ftest-coverage -I./../libar
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
These options require the collection of gcov data. I think you didn't
mean it, and they have been thrown in CFLAGS by mistake. Did you try
specifying CFLAGS either before or at the configure command?

I have to confess that I'm still running an old version of opendkim,
so I'm not sure what configuration option has triggered such settings.
  I guess this list is the right place to ask it, but you should post
your "configure" command too.
Received on Sun Aug 01 2010 - 12:12:11 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:19:48 PST