FreeBSD Port: samba34-3.4.14

Chuck Swiger cswiger at mac.com
Tue Apr 10 06:30:22 UTC 2012


On Apr 9, 2012, at 5:26 PM, Da Rock wrote:
[ ... ]
>> If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure.
> 
> I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer.

Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve.

>> However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine:
>> 
>>   http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log
>>   http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log
>>   http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log
> 
> Hmmm. You're right.
> 
> I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :)
> 
> So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one?

Don't know-- I don't recall having a build of Samba fail for me any time recently, but if you can confirm that a specific option causes the build failure, that would help reproduce.  Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency...

Regards,
-- 
-Chuck



More information about the freebsd-ports mailing list