Compiling problem for BASH 3.2
Alexander Dong Back Kim
I'm trying to compile BASH 3.2 on Minix. In the very first attemp, I
couldn't even execute 'configure' file because of not enough memory.
That one was easy one because I can just increase the memory stack
size of shell by using chmem.
During the compile, it was complaining about 'ld' so I made a symbolic
link to /bin from the i386-pc-minix directory so it was also solved.
After those, it seems to me the configure file worked out okay so it's
the time for executing 'make' file!
However, it had another weird error message about memory exhaustion of
command 'm4' so I did chmem for m4 like I did for bash.
Now I got this error message that I have no idea at all. I googled
this message but not a good one (or probably my searching ability
sucks).
bison -y -d ./parse.y
conflicts: 1 shift/reduce
touch parser-built
rm -f mksyntax
cc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -
DCONF_OSTYPE='"minix"' -DCONF_MACHTYPE='"i686-pc-minix"' -
DCONF_VENDOR='"pc"' -DLOCALEDIR='"/usr/local/share/locale"' -
DPACKAGE='"bash"' -DSHELL \
-DHAVE_CONFIG_H -I. -I. -I./include -I./lib -I./lib/intl -
I/home/dbkim/bash-3.2.tar/bash-3.2/lib/intl -g -o mksyntax ./
mksyntax.c
"./mksyntax.c", line 88: (warning) 'usage' old-fashioned function
definition
"./mksyntax.c", line 110: (warning) 'cdesc' old-fashioned function
definition
"./mksyntax.c", line 154: (warning) 'getcstr' old-fashioned function
definition
"./mksyntax.c", line 167: (warning) 'addcstr' old-fashioned function
definition
"./mksyntax.c", line 189: (warning) 'addcchar' old-fashioned function
definition
"./mksyntax.c", line 202: (warning) 'addblanks' old-fashioned function
definition
"./mksyntax.c", line 219: (warning) 'load_lsyntax' old-fashioned
function definition
"./mksyntax.c", line 258: (warning) 'dump_lflags' old-fashioned
function definition
"./mksyntax.c", line 284: (warning) 'wcomment' old-fashioned function
definition
"./mksyntax.c", line 295: (warning) 'dump_lsyntax' old-fashioned
function definition
"./mksyntax.c", line 317: (warning) 'main' old-fashioned function
definition
rm -f syntax.c
./mksyntax -o syntax.c
/bin/sh ./support/mkversion.sh -b -S . -s release -d 3.2 -o
newversion.h \
&& mv newversion.h version.h
mkversion.sh: 3.2: bad distribution version
make in /home/dbkim/bash-3.2.tar/bash-3.2: Exit code 1
Any idea?
The reason why I'm doing this is the current bash seems doesn't really
like to be run on Minix machine so I'm hoping this newer version works
okay with Minix 3.1.2a.
cheers,
AK
Alexander Dong Back Kim
wrote:
Hi all,
I've just realized that the configure file sets the makefile uses
Minix CC not GCC. I created another symbolic link for gcc and re-
executed the configure file and it seems it's not using GCC but
haven't compile yet.
cheers,
AK
Alexander Dong Back Kim
Same failure... =( Please give me any hint!!!
cheers,
AK
Alexander Dong Back Kim
Oh! I could soved the problem. The problem was related with the
running shell of Makefile. I changed Makefile's shell from /bin/sh to /
bin/bash, the compilation works just fine!!!
cheers,
AK
Alexander Dong Back Kim
Another error. In this time there was an error in the source codes...
I guess I really do need to start coding on some codes in order to
port bash for minix...
cheers,
AK
Greg King
> On Jul 12, 3:12 pm, Alexander Dong Back Kim wrote:
> >
> > I'm trying to compile BASH 3.2 on Minix. In the very first attempt, I
> > couldn't even execute 'configure' file because of not enough memory.
> > size of shell by using chmem.
> > link to /bin/ from the i386-pc-minix/ directory; so, it also was solved.
> > After those, it seems to me the configure file worked out OK; so, it's
> > the time for executing 'make' file!
> > However, it had another weird error message about memory exhaustion of
> >
[... snip ...]
> >
> > The reason why I'm doing this is that the current bash doesn't really
> > seem
> > to like to be run on Minix machine; so, I'm hoping this newer version
> > works
> > OK with Minix 3.1.2a.
>
> I've just realized that the configure file sets the makefile to use
> Minix CC, not GCC. I created another symbolic link for gcc, and re-
> executed the configure file; and, it seems it's now using GCC, but
> haven't compiled yet.
Is that symbolic link really needed? Maybe, there is a simpler work-around
for that configure bug: re-arrange the order of the paths in your PATH
environment variable. Put ":/usr/gnu/bin" in front of ":/bin:/usr/bin".
(Then, those broken configure scripts will find "gcc" before they find
"cc".)
Greg King
> > On Jul 12, 3:39 pm, Alexander Dong Back Kim wrote:
> > > On Jul 12, 3:12 pm, Alexander Dong Back Kim wrote:
> > > >
> > > > I'm trying to compile BASH 3.2 on Minix. In the very first attempt,
> > > > couldn't even execute 'configure' file because of not enough memory.
> > > > size of shell by using chmem.
> > > >
> > > > Now, I get this error message that I have no idea at all. I googled
> > > > this message, but not a good one (or, probably my searching ability
> > > > sucks).
> > > >
> > > > ./mksyntax -o syntax.c
> > > > /bin/sh ./support/mkversion.sh -b -S . -s release -d 3.2 -o
> > > > newversion.h \
> > > > && mv newversion.h version.h
> > > > mkversion.sh: 3.2: bad distribution version
> > > > make in /home/dbkim/bash-3.2.tar/bash-3.2: Exit code 1
>
> running shell of Makefile. I changed Makefile's shell from "/bin/sh"
That problem can be solved by setting (and exporting)
"CONFIG_SHELL=/bin/bash" before you run the configure script.