From: "T. P. Saravanan" <sara@procsys.com>
To: "T. P. Saravanan" <sara@procsys.com>
Cc: David Daney <ddaney@avtrex.com>, linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - Unknown ABI problem
Date: Thu, 07 Oct 2004 09:35:45 +0530 [thread overview]
Message-ID: <4164C099.5000503@procsys.com> (raw)
In-Reply-To: <4163710D.8020009@procsys.com>
T. P. Saravanan wrote:
> T. P. Saravanan wrote:
>
>> David Daney wrote:
>>
>>>> What should I do to fix the build?
>>>>
>>>
>>>
>>>
>>> get the most recent machine-gmon.h from glibc CVS.
>>>
>>> You will probably find a problem linking libc at a later step. But the
>>> newer machine-gmon.h will fix this problem.
>>>
>>>
>> OK. That worked. Thanks a lot.
>>
> Oops! I will take that back. I suspect it is not working.
>
> When you said CVS I assumed the one in http://linux-mips/cvsweb/libc.
> On closer
> look it looks very old. From discussions in another thread I gather
> CVS means
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/?cvsroot=glibc.
> (Correct me
> if this is wrong.) If I take the machine-gmon.h from here - It still
> has the
> same problem :-(
>
Correction Again: It works. I got the machine-gmon.h and builds all
mixed up. I did
a fresh compile and it went past this point.
[Sorry for all the confusion. I will post more carefully in future.]
-Sa.
next prev parent reply other threads:[~2004-10-07 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 5:50 mips linux glibc-2.3.3 build - Unknown ABI problem T. P. Saravanan
2004-10-04 16:19 ` David Daney
2004-10-05 9:03 ` T. P. Saravanan
2004-10-06 4:14 ` T. P. Saravanan
2004-10-07 4:05 ` T. P. Saravanan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-06 4:35 David Daney
2004-10-06 4:35 ` David Daney
2004-10-07 4:10 ` T. P. Saravanan
2004-10-08 10:55 ` T. P. Saravanan
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=4164C099.5000503@procsys.com \
--to=sara@procsys.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox