From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002874]: libglib2 does not build
Date: Mon, 7 Apr 2008 04:05:50 -0700 [thread overview]
Message-ID: <272677f0ce95a6fefc545af50e49d5d2@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=2874
======================================================================
Reported By: joedawson
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 2874
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 04-07-2008 00:47 PDT
Last Modified: 04-07-2008 04:05 PDT
======================================================================
Summary: libglib2 does not build
Description:
libglib2 fails to build. Is tested for ARM and x86 builds, giving the same
error:
make[4]: Entering directory
`/srv/br-svn/build_arm/libglib2-2.15.4/gobject'
make[4]: `glib-genmarshal' is up to date.
make[4]: Leaving directory
`/srv/br-svn/build_arm/libglib2-2.15.4/gobject'
echo "#ifndef __G_MARSHAL_H__" > xgen-gmh \
&& echo "#define __G_MARSHAL_H__" >> xgen-gmh \
&& /usr/bin/glib-genmarshal --nostdinc --prefix=g_cclosure_marshal
./gmarshal.list --header >> xgen-gmh \
&& echo "#endif /* __G_MARSHAL_H__ */" >> xgen-gmh \
&& (cmp -s xgen-gmh gmarshal.h 2>/dev/null || cp xgen-gmh
gmarshal.h) \
&& rm -f xgen-gmh xgen-gmh~ \
&& echo timestamp > stamp-gmarshal.h
/bin/bash: line 2: /usr/bin/glib-genmarshal: No such file or directory
make[3]: *** [stamp-gmarshal.h] Error 127
make[3]: Leaving directory
`/srv/br-svn/build_arm/libglib2-2.15.4/gobject'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/srv/br-svn/build_arm/libglib2-2.15.4'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/srv/br-svn/build_arm/libglib2-2.15.4'
make: *** [/srv/br-svn/build_arm/libglib2-2.15.4/.stamp_built] Error 2
======================================================================
----------------------------------------------------------------------
joedawson - 04-07-08 04:05
----------------------------------------------------------------------
correction: it relies on libglib2 to be installed on the development
machine. is it possible to have that tested in some way?
Issue History
Date Modified Username Field Change
======================================================================
04-07-08 00:47 joedawson New Issue
04-07-08 00:47 joedawson Status new => assigned
04-07-08 00:47 joedawson Assigned To => buildroot
04-07-08 00:47 joedawson File Added: config
04-07-08 04:05 joedawson Note Added: 0006434
======================================================================
next reply other threads:[~2008-04-07 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 11:05 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-07 7:47 [Buildroot] [buildroot 0002874]: libglib2 does not build bugs at busybox.net
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=272677f0ce95a6fefc545af50e49d5d2@busybox.net \
--to=bugs@busybox.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