public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Girard <thomas.g.girard@free.fr>
To: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Questions about build web documentation
Date: Sun, 12 Aug 2007 20:38:00 -0000	[thread overview]
Message-ID: <1186950854.3853.29.camel@micmac> (raw)
In-Reply-To: <1186655070.3747.12.camel@dijkstra.wildebeest.org>

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

Hello,

Le jeudi 09 août 2007 à 12:24 +0200, Mark Wielaard a écrit :
> > There's something I don't understand about this page: according to it
> > jdom, junit and junit packages are required to build frysk. But they're
> > not because they are available from frysk-imports. Am I missing
> > something? (Besides, using system versions of these libraries - as we do
> > for Debian frysk package - require tweaking some autotools files.)
> 
> This might be slightly outdated then. antlr and jdom jars are used from
> the system if found (see frysk-imports/configure.ac), for junit,
> cdtparser, jline and getopt, we do include the upstream sources (see the
> frysk-import/ subdirs) and compile those to jar files. Then in
> frysk-imports/bootstrap.sh (FILE_LIST) we feed those, and the detected
> antlr and jdom jars, to common/Makefile.gen.sh that creates a
> frysk-imports/Makefile.gen, that is included in the
> frysk-imports/Makefile.am so that we finally generate native shared
> libraries from them, which we link against. 

Thanks for the explanation.

Please review the attached patch for htdocs/build/index.html.

I'm wondering if tracker bugs sould be split for Ubuntu and Debian
releases the way they are for Red Hat?

Regards,

Thomas

[-- Attachment #2: htdocs_build.diff --]
[-- Type: text/x-patch, Size: 1281 bytes --]

diff -r 2937c08d9e68 htdocs/build/index.html
--- a/htdocs/build/index.html	Wed Aug 08 21:54:42 2007 +0000
+++ b/htdocs/build/index.html	Sun Aug 12 22:33:09 2007 +0200
@@ -58,10 +58,12 @@
 <a href="#f8">Fedora 8</a><br>
 <a href="#f7">Fedora 7</a><br>
 <a href="#fc6">Fedora Core 6</a><br>
+<a href="#ubuntu-gutsy">Ubuntu - Gutsy</a><br>
 <a href="#ubuntu-edgy">Ubuntu - Edgy</a><br>
 <a href="#ubuntu-breezy">Ubuntu - Breezy</a><br>
 <a href="#rhel5">RHEL 5</a><br>
 <a href="#rhel4">RHEL 4</a><br>
+<a href="#debian">Debian</a><br>
 </p>
 	      <!-- end logo -->
 	    </td>
@@ -124,6 +126,28 @@ bug's <a
 bug's <a
 href="/bugzilla/showdependencytree.cgi?id=2004">dependency
 tree</a>.
+
+</dd>
+
+<dt><a name="ubuntu-gutsy">Ubuntu (Gutsy Gibbon)</a><br>
+<a name="debian">Debian</a></dt>
+
+<dd>
+
+You will need to install the following packages:
+
+<pre>
+g++ binutils-dev make gcj java-gcj-compat-dev \
+libglade-java-dev libvte-java-dev antlr libjdom1-java \
+automake libtool pkg-config autotools-dev libaudit-dev \
+sharutils transfig libxml2-utils xmlto gs-gpl yelp
+</pre>
+
+<p>
+
+For additional updates, check the
+<a href="/bugzilla/showdependencytree.cgi?id=4290">Debian</a> or
+<a href="/bugzilla/showdependencytree.cgi?id=1976">Ubuntu</a> tracker bug.
 
 </dd>
 

  reply	other threads:[~2007-08-12 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  8:27 Thomas Girard
2007-08-09 10:24 ` Mark Wielaard
2007-08-12 20:38   ` Thomas Girard [this message]
2007-08-20 21:28     ` Phil Muldoon
2007-08-20 22:02       ` Thomas Girard
2007-08-21  7:31         ` Mark Wielaard

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=1186950854.3853.29.camel@micmac \
    --to=thomas.g.girard@free.fr \
    --cc=frysk@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).