All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: davidm@hpl.hp.com
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PA-Linux version of libunwind
Date: Sat, 4 Dec 2004 22:09:17 -0700	[thread overview]
Message-ID: <20041205050917.GA8057@colo.lackof.org> (raw)
In-Reply-To: <200412050119.iB51Jln3001654@napali.hpl.hp.com>

On Sat, Dec 04, 2004 at 05:19:47PM -0800, David Mosberger wrote:
...
> At the moment, the PA Linux support is available only via the
> bitkeeper repository at:
> 
> 	bk://unwind.bkbits.net/libunwind/
> 
> If you want to play with this, just be sure to read the README.

I read the README and learned I should be using gcc 3.4.x (and
debian testing default is gcc-3.3.4).

But I ran into a different (trivial) problem during the build:
...
make[1]: Leaving directory `/home/src/libunwind/tests'
Making all in doc
make[1]: Entering directory `/home/src/libunwind/doc'
latex2man -t ./libunwind.trans libunwind.tex libunwind.man
make[1]: latex2man: Command not found
make[1]: *** [libunwind.man] Error 127
make[1]: Leaving directory `/home/src/libunwind/doc'
make: *** [all-recursive] Error 1

apt-cache search latex2man and packages.debian.org didn't help.
Anyone have a clue which package latex2man is in?

thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2004-12-05  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-05  1:19 [parisc-linux] PA-Linux version of libunwind David Mosberger
2004-12-05  2:33 ` Grant Grundler
2004-12-05  3:04   ` John David Anglin
2004-12-06 19:17     ` David Mosberger
     [not found]     ` <20041205091640.GV6359@tausq.org>
2004-12-06 19:22       ` David Mosberger
2004-12-05  5:09 ` Grant Grundler [this message]
2004-12-05  5:15   ` David Mosberger
2004-12-06 16:07     ` Grant Grundler

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=20041205050917.GA8057@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=davidm@hpl.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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.