samba - Mar 2021 - Samba Compiled From Source, Where Are The SystemD Unit Files?

Figured that might be the case, I copied the Debian 10 unit files for 
smbd and nmbd, make the applicable changes, then discovered that smbd is 
is failing after compile, make, make test, make install all successful 
(on Pi 4 native, not a cross compile).? So am a bit surprised.? 
Environment is Raspberry Pi OS 32bit for ARMv7 HF.? Is there any thing 
special that needs to be done for Pi devices when compiling from 
source?? Beyond the obvious required packages before compile?? Would 
have expected ./configure to throw a fit if there was something special 
needed specific for Pi? Unfortunately, the Debian 10 buster variant of 
Raspberry Pi OS only has a Samba 4.9 version level and even the yet to 
be released (as stable) Raspberry Pi OS based on Bullseye only has 4.12 
included.? So I guess the package maintainers are a bit behind the curve 
given 4.14 is available as stable.? What started be down this path was 
the need for profiling support, which is not included by default in the 
Debian 10 packages.

-DD

On 03/23/2021 08:49, Rowland penny via samba wrote:
> On 23/03/2021 15:32, Dachshund Digital via samba wrote:
>> I am doing 'make install' step as I write this question.? Via
Google,
>> I only seem to find examples of the unit files for control/support AD 
>> features, but no example for how smbd, nmbd, etc., unit files should 
>> be staged, or created? Even the SambaWiki and Samba.org seem to 
>> ignore this subject? Am I just not finding such?? This should be 
>> pretty straight-forward right?
>>
>> -DD
>>
>>
>
> Samba does not supply systemd service files, this is left to package 
> maintainers. The easiest way would be to use your distro's files, 
> possibly modified for your PREFIX.
>
> Rowland
>
>
>

Oh, and... I missed this option last night apparently ./configure 
--systemd-install-services just does not do this by default, thinking 
this may generate the unit files?

-DD

On 03/23/2021 10:16, Dachshund Digital via samba wrote:
> Figured that might be the case, I copied the Debian 10 unit files for 
> smbd and nmbd, make the applicable changes, then discovered that smbd 
> is is failing after compile, make, make test, make install all 
> successful (on Pi 4 native, not a cross compile).? So am a bit 
> surprised.? Environment is Raspberry Pi OS 32bit for ARMv7 HF.? Is 
> there any thing special that needs to be done for Pi devices when 
> compiling from source?? Beyond the obvious required packages before 
> compile?? Would have expected ./configure to throw a fit if there was 
> something special needed specific for Pi? Unfortunately, the Debian 10 
> buster variant of Raspberry Pi OS only has a Samba 4.9 version level 
> and even the yet to be released (as stable) Raspberry Pi OS based on 
> Bullseye only has 4.12 included.? So I guess the package maintainers 
> are a bit behind the curve given 4.14 is available as stable.? What 
> started be down this path was the need for profiling support, which is 
> not included by default in the Debian 10 packages.
>
> -DD
>
> On 03/23/2021 08:49, Rowland penny via samba wrote:
>> On 23/03/2021 15:32, Dachshund Digital via samba wrote:
>>> I am doing 'make install' step as I write this question.?
Via
>>> Google, I only seem to find examples of the unit files for 
>>> control/support AD features, but no example for how smbd, nmbd, 
>>> etc., unit files should be staged, or created? Even the SambaWiki 
>>> and Samba.org seem to ignore this subject? Am I just not finding 
>>> such?? This should be pretty straight-forward right?
>>>
>>> -DD
>>>
>>>
>>
>> Samba does not supply systemd service files, this is left to package 
>> maintainers. The easiest way would be to use your distro's files, 
>> possibly modified for your PREFIX.
>>
>> Rowland
>>
>>
>>
>

On 23/03/2021 17:16, Dachshund Digital via samba wrote:
> Figured that might be the case, I copied the Debian 10 unit files for 
> smbd and nmbd, make the applicable changes, then discovered that smbd 
> is is failing after compile, make, make test, make install all 
> successful (on Pi 4 native, not a cross compile).? So am a bit 
> surprised.? Environment is Raspberry Pi OS 32bit for ARMv7 HF.? Is 
> there any thing special that needs to be done for Pi devices when 
> compiling from source?? Beyond the obvious required packages before 
> compile?? Would have expected ./configure to throw a fit if there was 
> something special needed specific for Pi? Unfortunately, the Debian 10 
> buster variant of Raspberry Pi OS only has a Samba 4.9 version level 
> and even the yet to be released (as stable) Raspberry Pi OS based on 
> Bullseye only has 4.12 included.? So I guess the package maintainers 
> are a bit behind the curve given 4.14 is available as stable.? What 
> started be down this path was the need for profiling support, which is 
> not included by default in the Debian 10 packages.

Easiest way out of this, go here: https://apt.van-belle.nl/

Stop compiling Samba yourself ?

Rowland