> -Original Message-
> From: Jack L. [mailto:xxjack1...@gmail.com]
>
> I solved the issue by pkg delete -f *samba* and then it reinstalled fine.
>
Worked for me too in the FreeBSD 11/i386 case that had the same build error as
you. The FreeBSD 11/amd64 build is still failing with the
On Thu, Mar 23, 2017 at 07:48:48AM +0100, Herbert J. Skuhra wrote:
> The Doctor skrev:
> >
> > All right anyone seeing a failure in compilation
> > due to a GSSAPI call?
>
> Why do you install Samba 4.3 and not 4.4?
>
> Are the samba ports still maint
> Hello Wolfgang,
>
> are you building with default options, or did you set some specific (e.g.
> DEVELOPMENT)?
>
> Best regards,
> Matthias
>
>
These are my options used (should be pretty much default to my knowledge):
# This file is auto-generated by 'make config'.
# Options for
Hello Wolfgang,
are you building with default options, or did you set some specific (e.g.
DEVELOPMENT)?
Best regards,
Matthias
Am Donnerstag, März 23, 2017 10:23 CET, "Meyer, Wolfgang"
schrieb:
> I am getting The Doctor's compilation issue for samba43 and samba44
I solved the issue by pkg delete -f *samba* and then it reinstalled fine.
On Thu, Mar 23, 2017 at 2:23 AM, Meyer, Wolfgang wrote:
> I am getting The Doctor's compilation issue for samba43 and samba44 on a
> FreeBSD 11.0/amd64 machine and Jack's compilation issue on a
I am getting The Doctor's compilation issue for samba43 and samba44 on a
FreeBSD 11.0/amd64 machine and Jack's compilation issue on a FreeBSD 11.0/i386
machine. The port (samba44) compiles fine on a FreeBSD 10.3/amd64 machine.
Regards,
Wolfgang
Follow HOB:
-
Herbert J Skuhra skrev:
>
> The Doctor skrev:
>>
>> All right anyone seeing a failure in compilation
>> due to a GSSAPI call?
>
> Why do you install Samba 4.3 and not 4.4?
>
> Are the samba ports still maintained?
>
> 4.2 discontinued (EOL)
The Doctor skrev:
>
> All right anyone seeing a failure in compilation
> due to a GSSAPI call?
Why do you install Samba 4.3 and not 4.4?
Are the samba ports still maintained?
4.2 discontinued (EOL)2016-09-07 -> expire?
4.3 discontinued (EOL)2017-03-07 -> expire?
4.4
On Wed, Mar 22, 2017 at 01:58:58PM -0700, Jack L. wrote:
> I'm seeing
>
> [2278/3479] Compiling source3/libsmb/libsmb_file.c
> runner cc -O2 -pipe -march=penryn -fno-omit-frame-pointer
> -DLIBICONV_PLUG -fno-color-diagnostics -fstack-protector
> -fno-strict-aliasing -fPIC -D_REENTRANT
I'm seeing
[2278/3479] Compiling source3/libsmb/libsmb_file.c
runner cc -O2 -pipe -march=penryn -fno-omit-frame-pointer
-DLIBICONV_PLUG -fno-color-diagnostics -fstack-protector
-fno-strict-aliasing -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS
-DSTATIC_smbclient_MODULES=NULL
On Sat, 16 Apr 2016 01:16:54 +1000, Dewayne Geraghty stated:
>Thanks for posting Frank; I also have this problem which O.Hartman has
>created the PR
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208767
>
>And MAKE_JOBS_UNSAFE makes no difference.
I am experiencing the same problem whether
On Fri, Apr 15, 2016 at 8:16 AM, Dewayne Geraghty wrote:
> Thanks for posting Frank; I also have this problem which O.Hartman has
> created the PR
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208767
>
> And MAKE_JOBS_UNSAFE makes no difference.
>
>
Most people
Thanks for posting Frank; I also have this problem which O.Hartman has
created the PR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208767
And MAKE_JOBS_UNSAFE makes no difference.
On 16 April 2016 at 00:28, Frank Seltzer wrote:
> I've been having this problem since
I've been having this problem since the port update a few days ago. I've
tried with and without CUPS set multiple times each and 'with' always
fails in the same place with the same error and 'without' always completes
successfully.
The ports/UPDATING file SAMBA entry dated 20160412 only
14 matches
Mail list logo