LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux From Scratch
User Name
Password
Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.

Notices

Reply
 
Search this Thread
Old 02-06-2003, 03:02 PM   #1
AxeZ
Member
 
Registered: Sep 2002
Location: Novi Sad, Vojvodina
Distribution: Slackware, FreeBSD
Posts: 386

Rep: Reputation: 32
Segfault on glibc


Ok, Im in Chapter 6 and just finished installing Glibc 2.3.1
Eveything is perfect so far but when I do

make localedata/install-locales && ( it takes a while )

exec /static/bin/bash --login <---this thing crash it hard so I am out of chroot really fast..

When I try to chroot back as explained in Entering the chroot environment it segfaults again, so I am unable to proceed.

Bash is 2.05b, gcc is 3.2.1 and glibc is 2.3.1

What can I do?
 
Old 02-06-2003, 04:48 PM   #2
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
My guess would be that your static version of bash was not configured properly or did not compile properly. Try recompiling the static version of bash and pay very close attention to the options and any prerequisites (i.e. the curses and ncurses libraries mentioned immediately before you compile bash).

As a personal preference, when I recompile software that gives me trouble, I delete its source tree (i.e. "rm -rf bash-2.05b"). Then I replace it by untar-ing the source from the packages again. It's not really necessary, but gives me a nice, warm, and fuzzy feeling.
 
Old 02-07-2003, 07:44 AM   #3
AxeZ
Member
 
Registered: Sep 2002
Location: Novi Sad, Vojvodina
Distribution: Slackware, FreeBSD
Posts: 386

Original Poster
Rep: Reputation: 32
Quote:
Originally posted by Dark_Helmet
My guess would be that your static version of bash was not configured properly or did not compile properly. Try recompiling the static version of bash and pay very close attention to the options and any prerequisites (i.e. the curses and ncurses libraries mentioned immediately before you compile bash).



IT didnt want to compile because it didnt find curses so I reconfigured and omitted --with-curses. It worked.
I dont believe that could cause problems.
Should I upgrade ncurses on My Slackware 8.1???


Quote:
As a personal preference, when I recompile software that gives me trouble, I delete its source tree (i.e. "rm -rf bash-2.05b"). Then I replace it by untar-ing the source from the packages again. It's not really necessary, but gives me a nice, warm, and fuzzy feeling.
True, true, I do the same.
 
Old 02-07-2003, 10:55 AM   #4
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
Well, two disclaimers first:

1) I've never tried compiling bash without the ncurses library
2) I've never had problems compiling bash with the exception of having to specify the system type for the configure scipt

In other words, any information following this should be prefaced with "I'm no expert, but this might work..."

To be honest, I don't exactly know what the ncurses library is used for. Removing it may leave bash lacking some functionality that LFS requires later down the road. That being my paranoid stance, I'd try to upgrade ncurses. I don't know what version LFS wants or what slackware comes bundled with, but since revision 4.0 of the LFS book was released within a month or two, I think it's safe to assume they were using a relatively recent version of the library.
 
Old 02-07-2003, 01:36 PM   #5
AxeZ
Member
 
Registered: Sep 2002
Location: Novi Sad, Vojvodina
Distribution: Slackware, FreeBSD
Posts: 386

Original Poster
Rep: Reputation: 32
Hmm, I guess Bash really needed curses.. compiled ncurses 5.3 ( on Slack 8.1 default is 5.2 ) and recompiled Bash with curses flag and now I can chroot normally
 
Old 02-07-2003, 02:32 PM   #6
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
Glad to hear it worked. I wish I could have given an exact explanation... Always something else to learn.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
problem installing glibc-2.3.2-4.80.i686, glibc-common-2.3.2-4.80.8.i386.rpm martianpackets Red Hat 8 05-01-2009 03:22 PM
2.6.11 kernel or glibc segfault everywhere..? Yerp Linux From Scratch 5 05-20-2005 03:42 PM
Replacing glibc using linuxthreads for glibc using nptl (native positx thread library CestusGW Linux From Scratch 4 01-20-2005 07:26 AM
ncsd, glibc, and glibc-common conflicts during LAMP install beaker911 Linux - Software 0 12-30-2004 02:31 PM
glibc 2.3.2 => glibc 2.3.3 causes bash & syslog issues natetheros Red Hat 1 09-27-2004 01:35 AM


All times are GMT -5. The time now is 11:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration