Bash compilation problems when creating an LFS system

Thread View: uk.comp.os.linux

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by "Mark. Hymers" Wed, 28 Mar 2001 12:09

#99818

Author: "Mark. Hymers"
Date: Wed, 28 Mar 2001 12:09

29 lines
1024 bytes

I am having a problem when compiling bash 2.04 using an old
Redhat 6.2 system.  I'm trying to set up an linux from
scratch system, but when I use --enable-static-link to compile
bash statically, the compilation stops part of the way through
with the message
warning: xxxxx.c using undefined symbol __yyyyy
(repeats for a while)
error: ld returned status 1
(or something like that).  If I compile it the normal way, I
don't have a problem.  Does anyone know what this could be
due to?

Also, can anyone tell me how to use ls to get a list of all the
files below the ls point with full paths.  I'm using ls -R1
but need it to give the full path, i.e. ./bin/bash instead
of just bash.  I'm trying to use the output of this with diff
to tell me which files have been installed by which package.
Is there a better way of doing this?

Thanks for any help

Mark

--
Mark.Hymers@ncl.ac.uk
University of Newcastle Medical School
** Opinions expressed are my own and not those **
**  of the University of Newcastle Upon Tyne   **

Re: Bash compilation problems when creating an LFS system

#99859

Author: Nix
Date: Wed, 28 Mar 2001 22:28

31 lines
1175 bytes

On 28 Mar 2001, Mark. Hymers uttered the following:
> I am having a problem when compiling bash 2.04 using an old
> Redhat 6.2 system.  I'm trying to set up an linux from
> scratch system, but when I use --enable-static-link to compile
> bash statically, the compilation stops part of the way through
> with the message
> warning: xxxxx.c using undefined symbol __yyyyy
> (repeats for a while)

We need *way* more information than that, but I'd *guess* the problem is
that you don't have static-library (.a) versions of one of libc,
libncurses, or libgpm (if you're using that). Get or build them and it
might work better.

> Also, can anyone tell me how to use ls to get a list of all the
> files below the ls point with full paths.  I'm using ls -R1

man find.

> but need it to give the full path, i.e. ./bin/bash instead
> of just bash.  I'm trying to use the output of this with diff
> to tell me which files have been installed by which package.

!?! RPM has a list option (-l, IIRC). Use that.

(find and diff?!? *boggle*)

--
`I've had my name crash computers. My name is a Word of Power.'
                                                       --- Peter da Silva

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads