Eray Aslan:
> On Tue, Jul 15, 2014 at 11:06:42AM +0000, Viktor Dukhovni wrote:
> > On Tue, Jul 15, 2014 at 10:07:30AM +0000, Eray Aslan wrote:
> > > I am trying to support those who cross compile postfix. They do have
> > > gcc installed but it is not the linker they want.
> >
> > Makes sense, you may need to patch this yourself if you can't convince
> > Wietse that "${CC} -shared ..." is a good idea for just any old "${CC}".
This is adopted into postfix-2.12-20140716.
> On a semi-related note, a bump in cross compiling postfix is the
> postconf command used in the postfix-install script. The script calls
> postconf to get mail version, config directory, installed defaults and
> to prepare main.cf for installation. However, in a cross compile
> environment, the bin/postconf binary is for a different architecture
> than the build host and therefore does not work.
Both the procedures that *build* Postfix and those that *install*
Postfix require programs and shared libraries(!) from that same
Postfix version. Without this I'd have a chicken and egg problem.
You are welcome to try to make those dependencies configurable,
from the "built" programs that are used now, to the "native" programs
that you want to use instead.
However, there is no reasonable way that I can support this. Those
"native" programs would have to be the same Postfix version, and
they would need to be built with similar-enough compile-time options
so that they will be "compatible enough" with the cross-compiled
product. The problem is that no-one can specify what "similar enough"
or "compatible enough" means. Thus, I cannot promise that something
is supported because I can't say what that means.
Wietse
