boot failure (and MOL) complete
Tanger
yellowdog-general@lists.terrasoftsolutions.com
Sat Nov 16 18:28:01 2002
--Apple-Mail-2--940206659
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Hello Steve,
Here the results:
> [root@pcp837989pcs root]# echo $PATH
>
> You should get something like.
> /bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:
> /usr/X11R6/bin:/root/bin
That is exactly what I got.
> Having done that type:
> 'c++' from anywhere to see if 'c++: No input file' shows up. If it does
> there should be no reason for it not to find c++. In should case it
> might be a problem with the Makefile.
'c++: No input file' does show up.
> Lets try building this rpm a little differently for you. As su:
>
> rpm -Uvh mol-0.9.65-1.src.rpm
> rpm -Uvh mol-kmods-0.9.65-1.src.rpm
[root@3-98-237-24-cable src]# rpm -Uvh mol-0.9.65-1.src.rpm
1:mol ###########################################
[100%]
[root@3-98-237-24-cable src]# rpm -Uvh mol-kmods-0.9.65-1.src.rpm
1:mol-kmods ###########################################
[100%]
> Now go to /usr/src/rpm/SPECS in there should be a .spec file for both
> mol and mol-kmods. To build them we:
>
> rpm -ta --clean mol.spec
> rpm -ta --clean mol-kmods.spec
[root@3-98-237-24-cable SPECS]# rpm -ta --clean mol.spec
mol.spec: No such file or directory
[root@3-98-237-24-cable SPECS]# ls
mol-kmods.spec mol.spec
[root@3-98-237-24-cable SPECS]# rpm -ta --clean mol-kmods.spec
mol-kmods.spec: No such file or directory
> Just out of curiosity does that problem occur for other command line
> utils? For example does 'vi .bashrc' in your ~?
I am not sure I am understanding this correctly. When I am in the
terminal and put in 'vi.bashrc' I get:
# .bashrc
# User specific aliases and functions
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
~
~
~
> Or try other stuff.
Like what?
> If the installing the rpm-devel didnt help we need to find out why as
> it may cause other *issues*. And *issues* are not good. :-)
:-)
Stefan
--Apple-Mail-2--940206659
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
Hello Steve,
Here the results:
<excerpt>[root@pcp837989pcs root]# echo $PATH
You should get something like.
/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin:/root/bin
</excerpt>
That is exactly what I got.
<excerpt>Having done that type:
'c++' from anywhere to see if 'c++: No input file' shows up. If it
does there should be no reason for it not to find c++. In should case
it might be a problem with the Makefile.
</excerpt>
'c++: No input file' does show up.
<excerpt>Lets try building this rpm a little differently for you. As
su:
rpm -Uvh mol-0.9.65-1.src.rpm
rpm -Uvh mol-kmods-0.9.65-1.src.rpm
</excerpt>
[root@3-98-237-24-cable src]# rpm -Uvh mol-0.9.65-1.src.rpm
1:mol
########################################### [100%]
[root@3-98-237-24-cable src]# rpm -Uvh mol-kmods-0.9.65-1.src.rpm
1:mol-kmods
########################################### [100%]
<excerpt>Now go to /usr/src/rpm/SPECS in there should be a .spec file
for both mol and mol-kmods. To build them we:
rpm -ta --clean mol.spec
rpm -ta --clean mol-kmods.spec
</excerpt>
[root@3-98-237-24-cable SPECS]# rpm -ta --clean mol.spec
mol.spec: No such file or directory
[root@3-98-237-24-cable SPECS]# ls
mol-kmods.spec mol.spec
[root@3-98-237-24-cable SPECS]# rpm -ta --clean mol-kmods.spec
mol-kmods.spec: No such file or directory
<excerpt>Just out of curiosity does that problem occur for other
command line utils? For example does 'vi .bashrc' in your ~?
</excerpt>
I am not sure I am understanding this correctly. When I am in the
terminal and put in 'vi.bashrc' I get:
# .bashrc
# User specific aliases and functions
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
~
~
~
<excerpt>Or try other stuff.
</excerpt>
Like what?
<excerpt>If the installing the rpm-devel didnt help we need to find
out why as it may cause other *issues*. And *issues* are not good. :-)
</excerpt>
:-)
Stefan
--Apple-Mail-2--940206659--