h.pellarin at scito-security.com
h.pellarin at scito-security.com
Wed Jan 15 07:10:35 PST 2003
first thanks for your support here that s nice of you.
i am a sys admin usualy work on bsd not unix and i like the idea of
buildin ur own linux,so i make a try.
everything went well till... the bash install
i do it from a mandrake 9.0
bfore install bash i got this:
[root at linsux bash-2.05a]# ln -s libncurses.a /usr/lib/libcurses.a
ln: `/usr/lib/libcurses.a': fichier existant.
[root at linsux bash-2.05a]#
and then i go into the bash dir for run:
./configure --enable-static-link \
--prefix=$LFS/static --with-curses &&
and then i get
<herve__> rm -f shell.o
<herve__> gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"'
-DCONF_VENDOR='"pc"' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include
-I./lib -g -O2 -c shell.c
<herve__> In file included from shell.h:41,
<herve__> from shell.c:48:
<herve__> externs.h:163: conflicting types for `gethostname'
<herve__> /usr/include/unistd.h:734: previous declaration of `gethostname'
<herve__> externs.h:196: conflicting types for `strncasecmp'
<herve__> /usr/include/string.h:277: previous declaration of `strncasecmp'
<herve__> make: *** [shell.o] Error 1
<herve__> [root at linsux bash-2.05a]#
<herve__> ln -s libncurses.a /usr/lib/libcurses.a
so i though it could be cause of ncurse cause 5-2 is needed but i have
what shall i do?
thx for your help
Bill's LFS Login wrote:
> Can you get your mailer to wrap at col 72?
> On Mon, 13 Jan 2003, Cole, David wrote:
>>My name is David and I am trying to learn the nuts and bolts of linux
> because we have a linux firewall where I work and it will eventually be
> up to me<snip>
>>bash ./configure: No such file or directory
>>What am I doing or what have I do wrong to get this output and how do I fix it?
> I see a couple of our folks have answered your specific question.
> Thought I would pass a couple general suggestions.
> First, read the "general" parts of the LFS book a couple of times to
> firmly embed certain procedures in your brain, like "... change into the
> directory that the untar created...". You are going to be hit with a lot
> of strange (and wonderful? and inconsistent, sometimes) new syntaxes and
> semantics when your grey matter has not yet established the foundations
> for them. Frequent (re)view will help.
> Second, hit the linux documentation project (TLDP) for some excellent
> docs on all things Linux and bash and hardware and... you name it. It
> will be well worthwhile for you and will also reinforce some of the new
> stuff that will be embedding itself in your brain.
> Third, re-read the sections in LFS about reporting problems. Giving
> sufficient (but not _way_too_much_) information on your first post will
> get you results faster and also reduce the load on those trying to
> *Important* When you have a reason to reinstall a package (failed 1st
> time, upgrade, whatever) be sure to remove the existing source directory
> and untar again. After install you can remove the source directory (but
> not the linux stuff in chapter 5) to save space and also assure you
> don't accidently use "dirty" source trees.
> Use copy and paste (if you can) to build your instructions, but *be
> sure* to try and read and understand those commands. It will pay
> dividends later down the road.
> LFS has a FAQ. Take a few moments to peruse it. Many questions you may
> encounter (including this one?) may be answered in there. It is worth
> downloading it to your local machine so you have instant access.
> Although the LFS search is down ATM (IIRC) while the new hosting is
> being established, a *large* number of questions you may have may be
> answered with a google for the linuxfromscratch archives. Use that
> search effectively to also save yourself some more time.
> Lastly, this group is quite helpful, but can be ... umm "short" when
> folks post without taking advantage of FAQ, google and so on before
> posting. So be sure a make a good first impression.
> Just passing this stuff on and wishing you a pleasnat LFSing experience.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message
More information about the lfs-support