All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Wolfgang Denk <wd@denx.de>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Error while rebuilding glibc for ELDK
Date: Wed, 10 Jul 2002 15:14:31 +0200	[thread overview]
Message-ID: <3D2C3337.FBC1283@imc-berlin.de> (raw)
In-Reply-To: 20020710123915.6ECE71086F@denx.denx.de


Wolfgang Denk wrote:
>
> In message <3D2C2468.A733D375@imc-berlin.de> you wrote:
> >
> > I am using Wolfgang's ELDK for my ppc linux development. It works very good.
> >
> > Thanks a million, Wolfgang!
>
> Thanks for the compliments :-)
>
You're welcome! :o)

> > But since I want to use a 2.4.19 kernel instead of the 2.4.4 I tried to rebuild
> > the glibc.
>
> What has the kernel  version  to  do  with  the  C  library  used  by
> applications?
>

For building an application the header files in /usr/include (i.e.
$(ELDK_ROOT)/ppc_8xx/usr/include are used.

We need newer header files than the on ethat come with your ELDK. So instead of
just copying the missing files and messing the whole system up I thought it
would be a good idea to rebuild the glibc using the 2.4.19 kernel headers. And
so getting a clean /usr/include path.

> > I pulled the glibc-2.2.1-0f.src.rpm from ftp.leo.org installed it in
> > /opt/ELDK/usr/src/denx/SRPMS and started rebuilding the glibc with
>
> Ummm... you mean you pulled the source RPM from the  ELDK  directory?
> Or what?

I meant that I did what you said in ftp.leo.org/pub/eldk/README.html in section
8 "Rebuilding ELDK Components". So I pulled
ftp://ftp.leo.org/pub/eldk/eldk-ppc-sources.tar and extracted
target\SRPMS\glibc-2.2.1-0f.src.rpm from it. This file I installed using
$(CROSS_COMPILE)rpm -i glibc-2.2.1-0f.src.rpm. So I got the glibc sources and
specs und /opt/ELDK/usr/src/denx/SOURCES.

Just like you said in your README.

>
> > scholz@pinguin:/opt/ELDK/usr/src/denx/SPECS> ppc_8xx-rpm -ba glibc.spec
> >
> > It all works well until the installation scripts:
> ...
> > So what's the problem here? Is the file "el.mo" broken? Can I skip this? (I am
> > sure I won't need el.mo)
>
> If I remember correctly, you're running on a SuSE  system?  We  never
> verified  building  in sucha n environment. Under RH-7.x (x=1,2,3) it
> works fine.

Hmm. That's right. It's SuSE 8.0. But the other .po files produced no errors.
BTW I had troubles with the file "zh_TW.po" as well.

I just deleted these two files (in /opt/ELDK/usr/src/denx/BUILD/glibc-2.2.1/po/)
and tried again: With success thsi time!

I've seen a couple of

ru_RU.KOI8-R...locales/ru_RU:1927: LC_COLLATE: syntax error
locales/ru_RU:1928: LC_COLLATE: syntax error
locales/ru_RU:1929: LC_COLLATE: syntax error
locales/ru_RU:1930: LC_COLLATE: syntax error
locales/ru_RU:1931: LC_COLLATE: syntax error
locales/ru_RU:1932: LC_COLLATE: syntax error
locales/ru_RU:1933: LC_COLLATE: syntax error
locales/ru_RU:1934: LC_COLLATE: syntax error
 done
ru_UA.KOI8-U...locales/ru_UA:1926: LC_COLLATE: syntax error
locales/ru_UA:1927: LC_COLLATE: syntax error
locales/ru_UA:1928: LC_COLLATE: syntax error
locales/ru_UA:1929: LC_COLLATE: syntax error
locales/ru_UA:1930: LC_COLLATE: syntax error
locales/ru_UA:1931: LC_COLLATE: syntax error
locales/ru_UA:1932: LC_COLLATE: syntax error
locales/ru_UA:1933: LC_COLLATE: syntax error
 done
sk_SK.ISO-8859-2... done
sl_SI.ISO-8859-2... done
sq_AL.ISO-8859-1... done
...

but now I have some new rpms to install:

scholz@pinguin:~> ls -l /opt/ELDK/usr/src/denx/RPMS/ppc
insgesamt 27392
-rw-r--r--    1 scholz   devel     8808762 Jul 10 15:09
glibc-devel-ppc_8xx-2.2.1-0f.ppc.rpm
-rw-r--r--    1 scholz   devel    11550455 Jul 10 15:08
glibc-ppc_8xx-2.2.1-0f.ppc.rpm
-rw-r--r--    1 scholz   devel     7615151 Jul 10 15:11
glibc-profile-ppc_8xx-2.2.1-0f.ppc.rpm
-rw-r--r--    1 scholz   devel       21174 Jul 10 15:11
nscd-ppc_8xx-2.2.1-0f.ppc.rpm


Cheers,

Steven

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

      reply	other threads:[~2002-07-10 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D2C2468.A733D375@imc-berlin.de>
2002-07-10 12:39 ` Error while rebuilding glibc for ELDK Wolfgang Denk
2002-07-10 13:14   ` Steven Scholz [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=3D2C3337.FBC1283@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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.