From: "Riley Williams" <Riley@Williams.Name>
To: "Jose A. Amador" <co2ja01@fastmail.fm>, Shane <vk3bvp@qsl.net>,
Linux Hams <linux-hams@vger.kernel.org>
Subject: RE: making apps
Date: Fri, 28 Mar 2003 08:26:38 -0000 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAMEAGCEAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030328041621.445F72B22C@www.fastmail.fm>
Hi Jose.
>>> Starting out with Mandrake 9.0, and trying to get ax25 up.
>>> Looked at pa3gcu's page, and followed instructions. Everything
>>> worked except make on ax25-apps-0.0.6, which bombed while
>>> making call. Of course, it all scrolls up and off the screen.
>>> Can someone point me to how to look at this (working at
>>> command prompt Ctrl-Alt-F1, so no xterm scrollbar :-)
>> Shift + page up | down
>>> so I can see better where exactly the bomb-out is? It's
>>> repeatable.
> You could also make a log of your compilation with something
> similar to:
>
> make > /tmp/making_apps 2>&1
>
> Hope this helps. Guess that ncurses might be related as you were
> suggested before. Shane's suggestion (using the rpm) could be
> the easy way out...
When it comes to making logs of what's going on, I generally do...
make 2>&1 | tee make.log
...as that puts the log on the screen and lets me watch what it's
doing, so I don't get bored watching an unchanging screen. Also, by
dropping the log in the current directory, I know what it relates to
if I forget to erase it and come back to it later.
Best wishes from Riley G7GOD / KB8PPG
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.465 / Virus Database: 263 - Release Date: 25-Mar-2003
next prev parent reply other threads:[~2003-03-28 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 2:39 making apps Dexter N Muir
2003-03-28 2:53 ` M Taylor
2003-03-28 3:59 ` Dexter N Muir
2003-03-28 5:14 ` Bob Nielsen
2003-03-28 6:25 ` Dexter N Muir
2003-03-28 16:28 ` Bob Nielsen
2003-03-28 2:57 ` Shane Deering
2003-03-28 4:16 ` Jose A. Amador
2003-03-28 4:31 ` w9ya
2003-03-29 22:07 ` Jose A. Amador
2003-03-28 8:26 ` Riley Williams [this message]
2003-03-28 17:39 ` Curt Mills, WE7U
[not found] <BKEGKPICNAKILKJKMHCACEBJCEAA.Riley@Williams.Name>
2003-03-28 20:22 ` Curt Mills, WE7U
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=BKEGKPICNAKILKJKMHCAMEAGCEAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=co2ja01@fastmail.fm \
--cc=linux-hams@vger.kernel.org \
--cc=vk3bvp@qsl.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