All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
To: rekha gvv <rekhagvvc@yahoo.co.in>
Cc: Linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: glibc 2.2.2  error
Date: 18 Nov 2002 14:21:51 +0100	[thread overview]
Message-ID: <1037625711.27283.22.camel@spawn> (raw)
In-Reply-To: <20021118122042.74002.qmail@web8001.mail.in.yahoo.com>


If you read the INSTALL file you would know that --with-headers should
point to the linux kernel headers. I guess the path could be right but
most probably not.


On Mon, 2002-11-18 at 13:20, rekha gvv wrote:
>
> Hello,
> I am setting up glibc for powerpc target but It gives
> me errors ..
> I have set the options
> CC=powerpc-linux-gcc
> ./configure --build=powerpc-linux \
> > --enable-add-ons=linuxthreads \
> > --with-headers=/usr/local/powerpc-linux/include
>
> But when u compile  it is not able to find the headers
> there ...
> it gives these errors ...
> so can anyone specify the right options to configure
> glibc.
>
>
> In file included from ../posix/bits/posix1_lim.h:126,
>                  from :1:
> ../linuxthreads/sysdeps/unix/sysv/linux/bits/local_lim.h:36:26:
> linux/limits.h: No such file or directory
> make[1]: *** [../bits/stdio_lim.st] Error 1
> make[1]: Leaving directory `/usr/src/glibc-2.2.2/csu'
> make: *** [csu/subdir_lib] Error 2
>
>
> thankyou!
>
>
>
--
Kenneth Johansson
Ericsson AB                       Tel: +46 8 404 71 83
Borgafjordsgatan 9                Fax: +46 8 404 72 72
164 80 Stockholm                  kenneth.johansson@etx.ericsson.se


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-11-18 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 12:20 glibc 2.2.2 error rekha gvv
2002-11-18 13:21 ` Kenneth Johansson [this message]
2002-11-18 16:53 ` William A. Gatliff
2002-11-19  1:11 ` Michael Habermann

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=1037625711.27283.22.camel@spawn \
    --to=kenneth.johansson@etx.ericsson.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rekhagvvc@yahoo.co.in \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.