Re: EXTERNAL: Re: Failed to Create Symbolic Link During Build

["Otten, Jeffrey" <jeffrey.otten@xxxxxxxx>]

Vito,
You're correct - it's a typo due to Microsoft auto correction. It is lib/systemd/system.
I just discovered that the systemd.mak file provided in Buildroot contains:

define SYSTEMD_INSTALL_SERVICE_AUTOVT
	ln -sf ../../../lib/systemd/system/getty@.service \
		$(TARGET_DIR)/lib/systemd/system/autovt@.service

I'll try changing /lib to /usr/lib

-----Original Message-----
From: Vito Caputo <vcaputo@xxxxxxxxxxx> 
Sent: Thursday, July 21, 2022 2:16 PM
To: Otten, Jeffrey (US) <jeffrey.otten@xxxxxxxx>
Cc: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: EXTERNAL: Re:  Failed to Create Symbolic Link During Build

On Thu, Jul 21, 2022 at 03:33:34PM +0000, Otten, Jeffrey wrote:
> I'm trying to build systemd 243.4 using Buildroot 2019.11. The lines listed below are generated during the build. I've googled but haven't come across any discussion of this issue.
> The directory /home/ottenj/elinux/build/buildroot/fvlinux/target/lib/system/system listed in the error below does not exist. However, the sym link does exist in the directory /home/ottenj/elinux/build/buildroot/fvlinux/target/usr/lib/system/system. Does anyone have a suggestion about how to fix this error?
> 
> ln -sf ../../../lib/system/system/getty@.service 
> /home/ottenj/elinux/build/buildroot/fvlinux/target/lib/system/system/a
> utovt@.service
> ln: failed to create symbolic link 
> '/home/ottenj/elinux/build/buildroot/fvlinux/target/lib/system/system/
> autovt@.service': No such file or directory
> 
> 

At a glance that path looks wrong, typically it's "lib/systemd/system/" not "lib/system/system/"

Regards,
Vito Caputo