From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 545] Webkit doesn't see gtk-doc.make
Date: Mon, 10 Aug 2009 09:25:31 +0000 (UTC) [thread overview]
Message-ID: <20090810092531.A17527770B@busybox.osuosl.org> (raw)
In-Reply-To: <bug-545-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=545
--- Comment #6 from Will Newton <will.newton@gmail.com> 2009-08-10 09:25:30 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > gtkdocize is attempting to run, it's just not in the path, see "Warning: not
> > running gtk-docize."
> >
> > Should we depend on host-libgtk2 to make sure gtkdocize is available?
> >
> > For now installing gtkdocize in your host system should let you build.
> >
>
> Hmmm I'm not sure that's true. I have gtk-doc installed and I can't
> autreconfigure packages that depends on gtk-doc.m4.
> If I remember, that's because automake is called with -I argument pointing to
> the staging directory.
>
> Installing gtk-doc in staging directory should solve the problem.
The autogen.sh script in webkit calls gtkdocize. If it is in the path it should
work, I don't think automake is involved at this point.
Can you call gtkdocize manually in the webit directory?
e.g.
# cd build_arch/webkit-r44552
# gtkdocize --copy
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2009-08-10 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 21:55 [Buildroot] [Bug 545] New: Webkit doesn't see gtk-doc.make bugzilla at busybox.net
2009-08-06 23:25 ` [Buildroot] [Bug 545] " bugzilla at busybox.net
2009-08-07 8:36 ` bugzilla at busybox.net
2009-08-07 8:43 ` bugzilla at busybox.net
2009-08-07 19:12 ` bugzilla at busybox.net
2009-08-07 21:26 ` bugzilla at busybox.net
2009-08-10 9:25 ` bugzilla at busybox.net [this message]
2010-02-06 22:48 ` bugzilla at busybox.net
2010-02-21 18:08 ` bugzilla 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=20090810092531.A17527770B@busybox.osuosl.org \
--to=bugzilla@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