From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Compiling Under Debian
Date: Sat, 18 Oct 2008 08:29:23 +0800 [thread overview]
Message-ID: <025102606CB84710BC7BE42BEC53F6F4@bouncy> (raw)
In-Reply-To: <20081017194650.GA4002@lnx3.holmesgrown.com>
apt-get install build-essential
or
apt-get install libc6-dev
Regards, Kerry.
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, October 18, 2008 3:46 AM
Subject: Compiling Under Debian
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
I've got a testing version of Lenny here but can't find the C standard
headers. I've installed every imaginable package pertaining to gcc
and friends but when I go to compile any c programs like espeakup, I
get not found errors all over the place for simple header files like
stdio.h, errno.h, and so forth. I know these to be standard c headers
but the basic gcc package in debian doesn't seem to have them. I also
installed libstd-6-4-3... but still no joy. What the hell am I
missing here? I like Debian's package management strategy but I really
wish they wouldn't split up some critical packages this way. As far
as right now is concerned, I cannot compile any c programs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREDAAYFAkj466oACgkQWSjv55S0LfGvqQCdEH7h/4LjWjh5T5bMGdyQ2Zdl
G2IAnjb/KgtlqsYOxZMW37qa996cLU4M
=yT3p
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Zachary Kline
` Chuck Hallenbeck
` Steve Holmes
` Chuck Hallenbeck
` Erik Heil
` Steve Holmes
` Gregory Nowak
` Steve Holmes
` Kerry Hoath
` Erik Heil
` Kerry Hoath
` Kerry Hoath
` John covici
` John covici
` Kerry Hoath [this message]
` Tony Baechler
` Steve Holmes
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=025102606CB84710BC7BE42BEC53F6F4@bouncy \
--to=kerry@gotss.net \
--cc=speakup@braille.uwo.ca \
/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).