From: Gary Thomas <gdt@linuxppc.org>
To: Satadru Pramanik <satadru@umich.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: /usr/include files
Date: Mon, 29 Mar 1999 15:54:56 +0100 (BST) [thread overview]
Message-ID: <XFMail.990329155456.gdt@linuxppc.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9903290441460.22943-100000@beer.pub.umich.edu>
On 29-Mar-99 Satadru Pramanik wrote:
>
> Exactly wher can I get a copy of all the files in the /usr/include dir? I
> have egcs 1.1.2, and glibc 2.1, and my compilation of MySQL is failing due
> to problems with the files in that dir. I already have my
> /usr/include/linux dir symlinked to a cvs updated src dir, so I just need
> to get these include files fixed, I think. Which rpm file would this be
> in? I have the RedHat 5.9 Starbuck SRPMS files, so I just need to know
> which one to use.
>
These files come from a myriad of sources.
The primary ones come from the GLIBC-devel package.
Others, such as the include files for TCL/TK, would come from other assorted
packages.
What kind of problems are you having? details, please.
------------------------------------------------------------------------
Gary Thomas |
email: gdt@linuxppc.org | "Fine wine is a necessity of
... opinions expressed here are mine | life for me"
and no one else would claim them! |
| Thomas Jefferson
------------------------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-03-29 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-29 9:44 /usr/include files Satadru Pramanik
1999-03-29 14:54 ` Gary Thomas [this message]
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=XFMail.990329155456.gdt@linuxppc.org \
--to=gdt@linuxppc.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=satadru@umich.edu \
/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 NNTP newsgroup(s).