Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] alsa-utils: install systemd sevice files
Date: Wed, 21 Nov 2018 23:03:03 +0100	[thread overview]
Message-ID: <20181121230303.44b6579f@gmx.net> (raw)
In-Reply-To: <20181121173514.GM2601@scaer>

Hello Yann,

On Wed, 21 Nov 2018 18:35:14 +0100, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Peter, All,
> 
> On 2018-10-30 23:41 +0100, Peter Seiderer spake thusly:
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Changes v1 -> v2:
> >   - fix symlinks (reported by ????? ??????????)
> > ---
> >  package/alsa-utils/alsa-utils.mk | 14 ++++++++++++++
> >  1 file changed, 14 insertions(+)
> > 
> > diff --git a/package/alsa-utils/alsa-utils.mk b/package/alsa-utils/alsa-utils.mk
> > index e9a45c675f..0c65082a14 100644
> > --- a/package/alsa-utils/alsa-utils.mk
> > +++ b/package/alsa-utils/alsa-utils.mk
> > @@ -82,4 +82,18 @@ define ALSA_UTILS_INSTALL_TARGET_CMDS
> >  	fi
> >  endef
> >  
> > +ifeq ($(BR2_PACKAGE_ALSA_UTILS_ALSACTL),y)
> > +define ALSA_UTILS_INSTALL_INIT_SYSTEMD
> > +	$(INSTALL) -D -m 0644 $(@D)/alsactl/alsa-restore.service \
> > +		$(TARGET_DIR)/usr/lib/systemd/system/alsa-restore.service
> > +	$(INSTALL) -D -m 0644 $(@D)/alsactl/alsa-state.service \
> > +		$(TARGET_DIR)/usr/lib/systemd/system/alsa-state.service
> > +	mkdir -p $(TARGET_DIR)/etc/systemd/system/sound.target.wants
> > +	ln -sf ../../../../lib/systemd/system/alsa-restore.service \
> > +		$(TARGET_DIR)/etc/systemd/system/sound.target.wants/alsa-restore.service
> > +	ln -sf ../../../../lib/systemd/system/alsa-state.service \
> > +		$(TARGET_DIR)/etc/systemd/system/sound.target.wants/alsa-state.service
> > +endef
> > +endif  
> 
> This does not works with that defconfig:
> 
> BR2_arm=y
> BR2_cortex_a53=y
> BR2_ARM_FPU_NEON_VFPV4=y
> BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
> BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_INIT_SYSTEMD=y
> BR2_PACKAGE_ALSA_UTILS=y
> BR2_PACKAGE_ALSA_UTILS_ALSACONF=y
> BR2_PACKAGE_ALSA_UTILS_AMIXER=y
> BR2_PACKAGE_ALSA_UTILS_APLAY=y
> BR2_PACKAGE_ALSA_UTILS_SPEAKER_TEST=y
> # BR2_TARGET_ROOTFS_TAR is not set
> 
> And fails with this error:
> 
> /usr/bin/install -D -m 0644 /home/ymorin/dev/buildroot/O2/build/alsa-utils-1.1.6/alsactl/alsa-restore.service /home/ymorin/dev/buildroot/O2/target/usr/lib/systemd/system/alsa-restore.service
> /usr/bin/install: cannot stat '/home/ymorin/dev/buildroot/O2/build/alsa-utils-1.1.6/alsactl/alsa-restore.service': No such file or directory
> 
> Care to have a look, please?

Should be fixed (besides the systemd/uclibc problems) with:

	https://patchwork.ozlabs.org/patch/1001417

Regards,
Peter

> 
> Regards,
> Yann E. MORIN.
> 
> >  $(eval $(autotools-package))
> > -- 
> > 2.19.1
> > 
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot  
> 

      reply	other threads:[~2018-11-21 22:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30 22:41 [Buildroot] [PATCH v2] alsa-utils: install systemd sevice files Peter Seiderer
2018-11-01 13:51 ` Thomas Petazzoni
2018-11-21 17:35 ` Yann E. MORIN
2018-11-21 22:03   ` Peter Seiderer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181121230303.44b6579f@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox