All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jordanc@Censoft.com>
To: linux-mips@oss.sgi.com
Cc: jasonk@censoft.com, markl@censoft.com
Subject: Compiling libc
Date: Mon, 30 Oct 2000 16:24:40 -0700	[thread overview]
Message-ID: <39FE0338.AAB08D9A@censoft.com> (raw)

This is one for all the libc folks out there..

I am running into some big problems trying to compile libc-001023 as
downloaded from the ftp site just the other day. 

Basically, after compiling everything, I start to verify my build and I
get the following whilst in the /iconv directory (actually, I get it all
over the place):

mips_41xx_le-gcc -nostdlib -nostartfiles -o iconv_prog
-Wl,-dynamic-linker=/opt/hardhat/devkit/mips/41xx_le/mipsel-hardhat-linux/lib/ld.so.1  
../csu/crt1.o ../csu/crti.o `mips_41xx_le-gcc
--print-file-name=crtbegin.o` iconv_prog.o 
-Wl,-rpath-link=..:../math:../elf:../dlfcn:../nss:../nis:../rt:../resolv:../crypt:../linuxthreads
../libc.so.6 ../libc_nonshared.a -lgcc `mips_41xx_le-gcc
--print-file-name=crtend.o` ../csu/crtn.o
../libc.so.6: undefined reference to `__pthread_initialize_minimal'

This is driving me up the wall and down the other side since it is
obvious that the linuxthreads directory is part of the rpath, and I know
that all of the pthreads libraries are compiled, so I can't find a
single reason why it doesn't work.  

A little background for you...  mips_41xx_le is actually the
mipsel-linux compiler under a different name (from the MontaVista CDK). 
I invoked my configure script as such:

./configure --enable-add-ons=linuxthreads
--prefix=/opt/hardhat/devkit/mips/41xx_le/mipsel-hardhat-linux
mipsel-hardhat-linux

I would really appreciate any patches, advice or therapy.

Jordan crouse

             reply	other threads:[~2000-10-30 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 23:24 Jordan Crouse [this message]
2000-10-31  2:14 ` Compiling libc Ralf Baechle

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=39FE0338.AAB08D9A@censoft.com \
    --to=jordanc@censoft.com \
    --cc=jasonk@censoft.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=markl@censoft.com \
    /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.