Recently, Somebody Somewhere wrote these words
Hi Declan Moriarty,
Let us know what you find. Either there is a bug in the page, your
system is somehow incomplete or performing strangely, or else you
used the wrong commands.
I got the package installed on chroot and went through
Hi Declan,
Tks for your advice.
Try the kernel headers... Are your old new systems running from the
same kernel? Same kernel headers installed? Presuming your old
system
is a previous LFS,The other big differences is the version of
everything you use.
I'm now working on FC3, the Host.
#
Hi Declan,
Further to my late posting, I still retain the original kernel which
was first built on LFS 6.1, making BLFS 6.1 dual boot. I'll boot to
the original kernel to install following package.
Remark:-
I tried to install xpdf-3.01 on BLFS 6.1
Hi Rainer,
Tks for your advice.
(Remark: still working on FC3, the Host)
bash-3.00$ ./configure --prefix=/usr --sysconfdir=/etc \
--with-freetype2-includes=/usr/include/freetype2 \
--enable-opi --enable-multithreaded --enable-wordlist
make
./configure: line 88: conf3448.sh:
Hi Declan,
Further to my posting re installing lesstif - Xpdf, Xpdt-3.00 has
beeninstalled on BLFS 6.1, not on chroot environment. Both
./configure and make install went through without complaint. Now
Xpdf started by running;
$ xpdf
reading .xpdf files.
I think mixing versions being
Recently, Somebody Somewhere wrote these words
bash-3.00$ su
Password:
[EMAIL PROTECTED]:/sources/lesstif-0.94.4# make
rootdir=/usr/share/doc/lesstif-0.94.4 install
You appear to be typing make enter install enter. This is wrong.
cd to the top source dir if you are not there. If you are,
Hi Declan,
Tks for your advice.
snip
You appear to be typing make enter install
enter. This is wrong.
Sorry, No. make rootdir=/usr/share/doc/lesstif-0.94.4
install is one line. I copied/pasted it from;
http://www.linuxfromscratch.org/blfs/view/svn/x/lesstif.html
the word wrap function of
Recently, Somebody Somewhere wrote these words
[EMAIL PROTECTED]:/sources/procmail-3.22# grep -ne 'install:'
It only hung there until I pressed [Ctrl]+c to
terminate the command.
That should have been
grep -ne 'install:' Makefile*
grep rootdir Makefile might also be interesting. Either
.
1)
[EMAIL PROTECTED]:/sources/lesstif-0.94.4# make
rootdir=/usr/share/doc/lesstif-0.94.4 install
mv -v /usr/X11R6/lib/X11/mwm /etc/X11
ln -v -s ../../../../etc/X11/mwm /usr/X11R6/lib/X11
ldconfig
make: *** No rule to make target `install'. Stop.
[EMAIL PROTECTED]:/sources/lesstif-0.94.4#
2
Stephen Liu wrote these words on 09/04/05 22:25 CST:
I tried to install lesstif and met following problem.
Steps performed as follows;
lesstif-0.94.4
[EMAIL PROTECTED]:/sources# tar jxf
lesstif-0.94.4.tar.bz2
[EMAIL PROTECTED]:/sources# cd lesstif-0.94.4
[EMAIL
through without complaint.
1)
[EMAIL PROTECTED]:/sources/lesstif-0.94.4# make
rootdir=/usr/share/doc/lesstif-0.94.4 install
mv -v /usr/X11R6/lib/X11/mwm /etc/X11
ln -v -s ../../../../etc/X11/mwm /usr/X11R6/lib/X11
ldconfig
make: *** No rule to make target `install'. Stop.
[EMAIL PROTECTED
Hi Chris,
Re-did it as follow;
bash-3.00$ rm -Rf /sources/lesstif-0.94.4
bash-3.00$ cd /sources/
bash-3.00$ tar -jxf lesstif-0.94.4.tar.bz2
bash-3.00$ cd lesstif-0.94.4
bash-3.00$ patch -Np1 -i
../lesstif-0.94.4-testsuite_fix-1.patch
./configure --prefix=/usr --disable-debug \
/usr/lib/libgmodule-1.2.so.0.0.10
make: *** No rule to make target `install'. Stop.
root:/sources/glib-1.2.10$ make check
make: *** No rule to make target `check'. Stop.
root:/sources/glib-1.2.10$ make install
chmod -v 755 /usr/lib/libgmodule-1.2.so.0.0.10
make: *** No rule to make target
:/sources/glib-1.2.10$ make install
chmod -v 755 /usr/lib/libgmodule-1.2.so.0.0.10
make: *** No rule to make target `install'. Stop.
That was all I got.
B.R.
SL
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See
`check'. Stop.
root:/sources/glib-1.2.10$ make install
chmod -v 755 /usr/lib/libgmodule-1.2.so.0.0.10
make: *** No rule to make target `install'. Stop.
That was all I got.
B.R.
SL
Was the patch command spread out over 2 lines, or is that just the
result of the email text wrapping? Also
Hi Chris,
Was the patch command spread out over 2 lines, or is
that just the
result of the email text wrapping? Also, did you
remove the source tree
and unpack it again?
Removed the source and re-extracted the tarball.
Steps performed as follows;
After removing the source tree,
root:/$
16 matches
Mail list logo