From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-next 2/3] package/google-breakpad: switch to the new git repository
Date: Sun, 28 May 2017 20:14:36 +0200 [thread overview]
Message-ID: <clgrvdxfme.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 1480263400-29605-2-git-send-email-romain.naour@gmail.com
Am Sun, 27 Nov 2016 17:16:39 +0100 schrieb Romain Naour:
> +GOOGLE_BREAKPAD_DEPENDENCIES = host-google-breakpad linux-syscall-
support
> +
> +HOST_GOOGLE_BREAKPAD_DEPENDENCIES = host-linux-syscall-support
> +
> +# Avoid using depot-tools to download this file.
> +define HOST_GOOGLE_BREAKPAD_LSS
> + $(INSTALL) -D -m 0644 \
> + $(HOST_DIR)/usr/include/linux_syscall_support.h \
> + $(@D)/src/third_party/lss/linux_syscall_support.h
> +endef
> +HOST_GOOGLE_BREAKPAD_POST_EXTRACT_HOOKS += HOST_GOOGLE_BREAKPAD_LSS
Hi,
I do not know whether I found a bug or not while currently testing an
allyesconfig with "make legal-info" only.
In this case the package linux-syscall-support was not installed to
staging, therefore linux_syscall_support.h cannot be installed by
_POST_EXTRACT_HOOKS breaking the google-breakpad-legal-info target:
/usr/bin/install: cannot stat '/home/bernd/buildroot/buildroot/output/
host/usr/i586-buildroot-linux-uclibc/sysroot/usr/include/
linux_syscall_support.h': No such file or directory
Is the legal-info target meant to be used that way, this means without
building the package first, or do the packages have to be built before?
In this case the problem would not exist.
Regards, Bernd
next prev parent reply other threads:[~2017-05-28 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 16:16 [Buildroot] [PATCH for-next 1/3] package/linux-syscall-support: new package Romain Naour
2016-11-27 16:16 ` [Buildroot] [PATCH for-next 2/3] package/google-breakpad: switch to the new git repository Romain Naour
2016-11-28 19:37 ` Romain Naour
2016-12-17 15:33 ` Thomas Petazzoni
2017-05-28 18:14 ` Bernd Kuhls [this message]
2017-05-28 18:51 ` Romain Naour
2017-05-28 20:17 ` Thomas Petazzoni
2016-11-27 16:16 ` [Buildroot] [PATCH for-next 3/3] package/google-breakpad: bump to the latest version Romain Naour
2016-12-17 15:34 ` Thomas Petazzoni
2016-12-17 15:14 ` [Buildroot] [PATCH for-next 1/3] package/linux-syscall-support: new package Thomas Petazzoni
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=clgrvdxfme.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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