From: James Buchanan <jamesbuch@iprimus.com.au>
To: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com>,
"Matt Juszczak" <matt@atopia.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: c++ question
Date: Fri, 27 Dec 2002 04:25:00 -0000 [thread overview]
Message-ID: <5.1.0.14.0.20021227062659.009e6ad0@pop.iprimus.com.au> (raw)
In-Reply-To: <x3lm2cy6cn.fsf@lifesupport.shutdown.com>
GNU autoconf, automake and libtool by Vaughan, Elliston, Tromey and Taylor
published by New Riders. Excellent book and good tutorial and
reference. For make, try the GNU Make book published by the FSF
Press. There is "Using and Porting GCC" or something like that, also
published by the FSF Press. If you get that, also get the GNU C Library
book by the FSF Press. All excellent books, and all available free in
postscript format, too (the FSF ones.) I usually print these and stick
them in ringbinders since there is no way I can afford to buy all these books.
At 10:37 AM 12/26/2002 -0800, LLeweLLyn Reese wrote:
>"Matt Juszczak" <matt@atopia.net> writes:
>
> > Is there a good book that not only brushes up C/C++ skills but also focuses
> > on Makefiles, etc. (GNU-make, GNU-gcc, autoconf, etc.)
>[snip]
>
>$info make
>$info gcc
>$info autoconf
>
>:-)
>
>I don't know of a good book on any of make, gcc, or autoconf, except
> their respective info documentation. I wish I did. The gnu make
> info pages have an excellent tutorial, the autoconf pages a
> mediocre tutorial. The gcc info pages are a wonderful reference,
> but, I fear, quite confusing to those not already familiar with
> its convention.
>
>www.accu.org has excellent book reviews of many, many books, on many
> subjects (but mostly on C, C++, and Java.)
next prev parent reply other threads:[~2002-12-26 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 13:30 John Burski
2002-12-25 16:22 ` Alexander Helm
2002-12-26 2:26 ` LLeweLLyn Reese
2002-12-26 9:17 ` Matt Juszczak
2002-12-26 11:25 ` LLeweLLyn Reese
2002-12-27 4:25 ` James Buchanan [this message]
2002-12-27 4:56 ` LLeweLLyn Reese
2002-12-29 5:43 ` Ben Elliston
2002-12-29 6:09 ` LLeweLLyn Reese
2002-12-26 10:39 ` [SCALUG] " John Burski
2002-12-27 8:06 ` Andrea 'fwyzard' Bocci
2002-12-27 9:56 ` John Burski
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=5.1.0.14.0.20021227062659.009e6ad0@pop.iprimus.com.au \
--to=jamesbuch@iprimus.com.au \
--cc=gcc-help@gcc.gnu.org \
--cc=llewelly@lifesupport.shutdown.com \
--cc=matt@atopia.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).