On 6/4/20 11:55 AM, Pierre Labastie wrote:
On Thu, 2020-06-04 at 11:29 -0400, James Michmerhuizen wrote:
I am having a problem with jhalfs that is driving me nuts. I hope
somebody there can point me in a useful direction for help.
First a little background: I've been intermittently building LFS for
around ten years, for fun and learning. Recently started to use
jhalfs.
I've been away for a while; my last build effort, in 2017, yielded
a
primitive windowing environment but nothing that I could really
substitute for my Linuxmint programming habits.
Two days ago I made a fresh start, with a freshly downloaded (via
svn)
copy of jhalfs. Configured for no kernel, no systemd, SVN version
rather than book. There were no problems; the build completed
normally
in four hours.
So yesterday I started another moderately more ambitious
build. This
time we'll build a kernel, I thought. It took me a little while to
get
a .config file (I unpacked the kernel package to a location entirely
outside the jhalfs world and ran 'make defconfig' there), and then
it
took me a little while longer to figure out that I needed to specify
the
location of that .config with an absolute pathname.
The build started around 3pm.
It failed. And I haven't been able to figure out why.
Here are the error messages (following the fiveline header of my log
entry) that terminated the jhalfs make session:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
jim: 08:14 PM Wed, 03 Jun 2020
host-A:Mint-19.3:/Proj/LFS
tags: and THIS MORNINGS ERROR HAS RECURRED.
Building the system...
make[1]: Entering directory '/Proj/LFS/bld/jhalfs'
-------------------------------------------------------------------
-------------
mk_SETUP
stty: 'standard input': Inappropriate ioctl for device
--------------------------------------------------
Terminal too small: columns x lines
Minimum: 80 columns x 24 lines
--------------------------------------------------
Makefile:78: recipe for target 'ck_terminal' failed
make[1]: *** [ck_terminal] Error 1
make[1]: *** Waiting for unfinished jobs....
ROOT privilege is required to perform a number of commands
sudo will request a password in order to execute all high privilege
commands
-------------------------------------------------------------------
-------------
Building target save-luser
User lfs exists with ID 1001
Target save-luser OK
-------------------------------------------------------------------
-------------
-------------------------------------------------------------------
-------------
Building target 026-creatingtoolsdir
Makefile:207: recipe for target '026-creatingtoolsdir' failed
make: *** [026-creatingtoolsdir] Error 1
Makefile:88: recipe for target 'mk_SETUP' failed
make[1]: *** [mk_SETUP] Error 2
make[1]: Leaving directory '/Proj/LFS/bld/jhalfs'
ERROR: Error 2 at common/common-functions line 39!
<jhalfs> exit
Makefile:12: recipe for target 'all' failed
make: *** [all] Error 2
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
Based on these messages, I've looked at the relevant makefile
targets,
I've examined "common/common-functions line 39" and found nothing
that
could really explain the source of the error.
Any suggestions for me? This is an avocation, not a job; I'm long
retired, with time to investigate things. I'll appreciate anything
you
can tell me.
Hi Jim,
First, make should stop at first error, and not "Wait for unfinished
jobs". I guess you have MAKEFLAGS set to -jN, with N>1. The first error
comes from make being unable to run stty, apparently.
I must say that I have not tested with ticking
"General Settings -> Run the makefile".
First can you issue "stty size", and see if it returns meaningful line
and column numbers? If not, then there is a problem with the terminal
settings that I have never seen, so We'll have to discuss more...
Then try: make -C /Proj/LFS/bld/jhalfs
(I understand that you install your LFS system in /Proj/LFS/bld; if it
is not the case, then change accordingly.
If there is still an error in 026-creatingtoolsdir, then you can try to
examine the /Proj/LFS/bld/jhalfs/logs/000-masterscript file
HTH
Pierre
Another thing I recommend is seeing if /tools is present on your system.
If it is, move it out of the way. I've encountered this before when
starting a new jhalfs run and always move /tools to /tools.old (if the
system has anything in there that pertains to the current install of LFS
on it), or removing it if it's just the symlink that's present. In your
case, you'll want to remove or move /proj/LFS/bld/tools and /tools
(again, if they're present)
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
