problem compiling postfix2.0.x

[jdanieli]

Have you found a fix to the problem yet? I am having the same problem compiling postfix2.0.x. None of the 2.0.x versions will compile but all of the 1.1.11xxxxx versions will compile. I am also getting a similar error message.

If you find out what's wrong let me know.

JoeD

[pjp]

Can you post the last 20-30 lines of the error message?

Split from another thread.
_________________
Quis separabit? Quo animo?

[jdanieli]

I have been investigating this further and it appears the emerge postfix-2.0.9-r1 or any 2.0.x version does not compile the source files. If I go to /usr/tmp/portage/postfix-2.0.9-r1/work/postfix-2.0.9 and do a
make tidy
make -f Makefile.init makefiles
make
it will compile the source files. BUT if I do an emerge postfix it seems to go through the make makefiles part without any errors but when it is suppose to be compiling I get this sort of stuff
DHAS_SSL -DHAS_PCRE -march=athlon-xp -mcpu=athlon-xp -03 -pipe -I. -DLINUX2 -c
dict_sdbm.c
make: DSH_SSL : commanf not found
make: [host_port.o] Error 127 (ignored)
make: [sdbm.0] Error 127 (ignored)
ar rv libutil.a alldig.o ...... _sdbm.o sdbm.o
ar : alldig.o : no such file or directory
make: *** [libutil.a] Error 1
make: *** [update] Error 1

!!! ERROR net-mail/postfix-2.0.9-r1 failed
!!! Function src_compile, Line 114 Exitcode 2
!!! Compile problem

To me it appears it is not inserting the compiler name (gcc) at the beginning of the compile line. But since I'm not very familiar with make files I could be wrong.

I could just compile and install it without doing an emerge but then I defeat the reason I installed Gentoo to begin with which was to be able to update my software easily and always know I have the latest version.

Any ideas on how to fix this?

Thanks for your help

BTW my system is very spartan without any windowing systems on it. I tried to capture the errors into a file with
emerge postfix > errorfile
but all the errors still went to the console while the echoed commands went to the file.

JoeD

[Genone]

First, postfix 2.0.9 compiled fine on my machine, so it's not an error with the ebuild (unless you modified it). Before emerging try

[jdanieli]

Well I tried that but after I did it all my env variables were messed up. Sooo that made me research the problem and figure out where they were set. Once I got them working again I tried to emerge postfix again and it still did not work. Not to ever admit defeat I still felt that the compiler name was not being added to the beginning of the compile string so I added a few echo statements to the ebuild file and found that ${CC} was a null string. I first inserted CC=gcc into the ebuild file and lo and behold it started to compile. OK this is a good start in that I know what is wrong but not a good solution. I then inserted CC="gcc" into the enviornmental variables and that fixed the problem.

[Ferdy]

I also had to call emerge this way: