[Dovecot] 1.1b13 build in FreeBSD fails using 'make'; 'gmake' apparently required

[mikkel at euro123.dk]

On Mon, December 31, 2007 1:16 pm, Gerard wrote:
> On Mon, 31 Dec 2007 12:56:16 +0100
> Riemer Palstra <riemer at palstra.com> wrote:
>
>
>> On Mon, Dec 31, 2007 at 06:49:53AM -0500, Gerard wrote:
>>
>>> Might I suggest the following:
>>>
>>>
>>> 1) Contact the Dovecot port maintainer and inform him/her of your
>>> problem. They may not be aware of it, or it might be something else.
>>
>> But isn't the problem that the OP is *not* using the port? Assuming
>> that e.g. make will always be GNU make, or tar always being GNU tar,
>> isn't the best bet on most platforms.
>
> If he is not using the port and I fail to see any any good reason not
> to, then he is pretty much on his own. Putting a 'WARNING' notice up on
> 'wiki' probably would not be a bad idea. It might server to prevent
> other users from wasting this forum's time with these sort of postings.
> Expecting Timo to craft a special build niche build is absurd. He
> already is working far too hard keeping Dovecot ahead of the pack.
>
> There is also the possibility that the OP needs some special function or
> handling of Dovecot that the port does not support. Informing the
> maintainer would be a good way of getting this sort of matter taken care
> of. The OP did not express any special needs, and my crystal ball is off
> for the holidays, so I am not able to fathom what they might or might not
> be.
>
> By the way, I would have thought that it was obvious that make != gmake.
>

Calm down please.
There are many good reasons for not using the port.

Dovecot is constantly releasing new betas that should be tested and it
might not be feasible to wait for them to go into ports.

On top of this the HG development never will make it into ports.

Now the point of releasing the betas is that the users should test them.
That may be somewhat difficult if the users are told to bugger off when
they complain that the betas won't compile.

Compile errors are actually put into the development tree from time to
time (there appear to be other compile errors with this specific beta
release as well) so reporting it to the list makes perfectly sense.


After all the feedback comes from the users.

Regards (and a happy new year), Mikkel.