All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boszormenyi Zoltan <zboszor@pr.hu>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: systemtap fails to build
Date: Wed, 12 Mar 2014 12:09:45 +0100	[thread overview]
Message-ID: <53204079.9030806@pr.hu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hi,

I was trying to "bitbake core-image-lsb-sdk" and it failed with the error below.
Even after "repo sync ; bitbake -c clean systemtap"

| In file included from /usr/include/stdio.h:27:0,
|                  from 
/home/zozo/fsl-community-bsp/build-master-next/tmp/work/x86_64-linux/systemtap-native/2.5+gitAUTOINC+508059f048-r0/git/staprun/staprun.h:18,
|                  from 
/home/zozo/fsl-community-bsp/build-master-next/tmp/work/x86_64-linux/systemtap-native/2.5+gitAUTOINC+508059f048-r0/git/staprun/staprun.c:24:
| /usr/include/features.h:148:3: error: #warning "_BSD_SOURCE and _SVID_SOURCE are 
deprecated, use _DEFAULT_SOURCE" [-Werror=cpp]
|  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
|    ^
| cc1: all warnings being treated as errors
| make[3]: *** [staprun-staprun.o] Error 1

I am using a hybrid system, host is mostly Fedora 20 with some
packages upgraded from Rawhide, like GLIBC 2.19.90.
The attached (shortsighted) patch allows it to build here.

Best regards,
Zoltán Böszörményi


[-- Attachment #2: systemtap.patch --]
[-- Type: text/x-patch, Size: 2057 bytes --]

diff --git a/meta/recipes-kernel/systemtap/systemtap/systemtap-_BSD_SOURCE.patch b/meta/recipes-kernel/systemtap/systemtap/systemtap-_BSD_SOURCE.patch
new file mode 100644
index 0000000..62afbd2
--- /dev/null
+++ b/meta/recipes-kernel/systemtap/systemtap/systemtap-_BSD_SOURCE.patch
@@ -0,0 +1,27 @@
+diff --git a/staprun/staprun.c b/staprun/staprun.c
+index e4ced77..1db6f5b 100644
+--- a/staprun/staprun.c
++++ b/staprun/staprun.c
+@@ -13,21 +13,21 @@
+  * but WITHOUT ANY WARRANTY; without even the implied warranty of
+  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+  * GNU General Public License for more details.
+  *
+  * You should have received a copy of the GNU General Public License
+  * along with this program.  If not, see <http://www.gnu.org/licenses/>.
+  *
+  */
+ 
+ #define _XOPEN_SOURCE
+-#define _BSD_SOURCE
++#define _DEFAULT_SOURCE
+ #include "staprun.h"
+ #include "../privilege.h"
+ #include "../runtime/k_syms.h"
+ #include <string.h>
+ #include <sys/uio.h>
+ #include <glob.h>
+ #include <time.h>
+ #include <sys/prctl.h>
+ #include <sys/utsname.h>
+ 
diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc b/meta/recipes-kernel/systemtap/systemtap_git.inc
index 56db7b2..72cd313 100644
--- a/meta/recipes-kernel/systemtap/systemtap_git.inc
+++ b/meta/recipes-kernel/systemtap/systemtap_git.inc
@@ -1,18 +1,19 @@
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 SRCREV = "508059f04842ed85d10bfbec8a9c688d57368860"
 PV = "2.5+git${SRCPV}"
 
 SRC_URI = "git://sourceware.org/git/systemtap.git \
            file://docproc-build-fix.patch \
            file://obsolete_automake_macros.patch \
+           file://systemtap-_BSD_SOURCE.patch \
           "
 
 FILESPATH = "${FILE_DIRNAME}/systemtap"
 
 # systemtap doesn't support mips
 COMPATIBLE_HOST = '(x86_64|i.86|powerpc|arm|aarch64).*-linux'
 
 S = "${WORKDIR}/git"
 
 # systemtap can't be built without optimization, if someone tries to compile an

             reply	other threads:[~2014-03-12 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 11:09 Boszormenyi Zoltan [this message]
2014-03-12 15:05 ` [meta-freescale] systemtap fails to build Otavio Salvador
2014-03-12 15:05   ` Otavio Salvador

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=53204079.9030806@pr.hu \
    --to=zboszor@pr.hu \
    --cc=meta-freescale@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.