hi timo,
> Oh, that's different then. The Makefiles generated by autotools pretty
> much require GNU make.
then it's known/understood. great.
> Only after I make a release with "make dist" the
> generated Makefiles work with all makes.
ah. good to know.
> I'll add a note of this to the wiki p
On Tue, 2008-01-01 at 11:42 -0800, snowcrash wrote:
> > I can't reproduce this with FreeBSD 6.2. unicodemap.c is distributed in
> > the tarball, so I don't know why it would give that error.
>
> it's fully reproducible here.
>
> note that i'm not using the tarball. rather, pulling the hg 11b13 t
> I can't reproduce this with FreeBSD 6.2. unicodemap.c is distributed in
> the tarball, so I don't know why it would give that error.
it's fully reproducible here.
note that i'm not using the tarball. rather, pulling the hg 11b13 tag
clone. there, there's apparently *no* unicodemap.c included:
On Sun, 2007-12-30 at 22:02 -0800, snowcrash wrote:
> make
> make all-recursive
> Making all in src
> Making all in lib
> make: don't know how to make unicodemap.c. Stop
I can't reproduce this with FreeBSD 6.2. unicodemap.c is distributed in
the tarball, so I don't k
On 12/31/2007, Jeff Grossman ([EMAIL PROTECTED]) wrote:
I disagree with that statement. I think the OP was stating that the
build instructions on the wiki never mention anything about possibly
having to use gmake instead of make in a FreeBSD system. I think it
was very usual information that
Gerard wrote:
On Mon, 31 Dec 2007 08:12:24 -0800
snowcrash <[EMAIL PROTECTED]> wrote:
hi frank,
Yes, that's true. But I had never problems to test new versions
with a modified port. I copied the port files to a new directory
and changed the Makefile, e.g.:
(snip)
This wo
On Mon, 31 Dec 2007 08:12:24 -0800
snowcrash <[EMAIL PROTECTED]> wrote:
> hi frank,
>
> > Yes, that's true. But I had never problems to test new versions
> > with a modified port. I copied the port files to a new directory
> > and changed the Makefile, e.g.:
> (snip)
> > This works on FreeBSD-7 i
hi frank,
> Yes, that's true. But I had never problems to test new versions with a
> modified port. I copied
> the port files to a new directory and changed the Makefile, e.g.:
(snip)
> This works on FreeBSD-7 in a jail.
that's good to know. thanks!
(btw, what were your base JAIL buildworld mak
On Mon, 31 Dec 2007 16:46:26 +0100
"Frank Behrens" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on 31 Dec 2007 14:44:
> > 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
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on 31 Dec 2007 14:44:
> 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.
Yes, that's true. But I had never problems
On Mon, 31 Dec 2007 06:35:34 -0800
snowcrash <[EMAIL PROTECTED]> wrote:
[snip]
> > By the way, I would have thought that it was obvious that make !=
> > gmake.
>
> Considering that it is on OSX,
>
> ls -al `which make` `which gmake` `which gnumake`
>-rwxr-xr-x 1 rootwheel 316576 2007
hi mikkel,
> 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.
1st, thanks for the comments :-) certainly no skin off my nose --
that's why newsreaders h
> > 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.
Riemer is correct. I am NOT using the port. Rather, I am doing a
build from src, and following the posted ins
On Mon, December 31, 2007 1:16 pm, Gerard wrote:
> On Mon, 31 Dec 2007 12:56:16 +0100
> Riemer Palstra <[EMAIL PROTECTED]> 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/he
On Mon, 31 Dec 2007 12:56:16 +0100
Riemer Palstra <[EMAIL PROTECTED]> 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
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
On Sun, 30 Dec 2007 22:02:42 -0800
snowcrash <[EMAIL PROTECTED]> wrote:
> hi,
>
> i'm doing a 1st build of dovecot in a freebsd 62R jail.
>
> following instructions at
>
> http://wiki.dovecot.org/CompilingSource
>
> ./configure
> make
> sudo make
hi,
i'm doing a 1st build of dovecot in a freebsd 62R jail.
following instructions at
http://wiki.dovecot.org/CompilingSource
./configure
make
sudo make install
after an OK 'configure', @ 'make', i get
make
make all-recu
18 matches
Mail list logo
