Trying to instal cp2k using g95 it does't find yacc. See attached

107 views
Skip to first unread message

Victor Calvo

unread,
May 14, 2013, 12:34:26 PM5/14/13
to cp...@googlegroups.com
make LDFLAGS= -C /home/vcalvop/cp2k-2.3/makefiles/../obj/Linux-x86-64-g95/tools -f /home/vcalvop/cp2k-2.3/makefiles/../makefiles/Makefile makedepf90
make[1]: Entering directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools'
test -d /home/vcalvop/cp2k-2.3/makefiles/../obj/Linux-x86-64-g95/tools/makedepf90-build || ( mkdir makedepf90-build ; cp /home/vcalvop/cp2k-2.3/makefiles/../tools/makedepf90/* makedepf90-build )
{ cd makedepf90-build ; ./configure --prefix=/home/vcalvop/cp2k-2.3/makefiles/../obj/Linux-x86-64-g95/tools --bindir=/home/vcalvop/cp2k-2.3/makefiles/../obj/Linux-x86-64-g95/tools ; make VERSION="2.8.8cp2k" ; make install ; }
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for flex... no
checking for lex... no
checking for yywrap in -lfl... no
checking for yywrap in -ll... no
checking for bison... no
checking for byacc... no
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for working alloca.h... yes
checking for alloca... yes
checking for strcasecmp... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
make[2]: Entering directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools/makedepf90-build'
yacc  find_dep.y
make[2]: yacc: Command not found
make[2]: *** [find_dep.c] Error 127
make[2]: Leaving directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools/makedepf90-build'
make[2]: Entering directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools/makedepf90-build'
yacc  find_dep.y
make[2]: yacc: Command not found
make[2]: *** [find_dep.c] Error 127
make[2]: Leaving directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools/makedepf90-build'
make[1]: *** [makedepf90] Error 2
make[1]: Leaving directory `/home/vcalvop/cp2k-2.3/obj/Linux-x86-64-g95/tools'
make: *** [deptool] Error 2


HELP :-)

--- Dr. V. Calvo-Perez ---
8 392 1991
CHILE
"Große Geister haben stets heftige Gegnerschaft in den Mittelmäßigen gefunden.“ A. Einstein

Urban Borštnik

unread,
May 15, 2013, 3:31:33 AM5/15/13
to cp...@googlegroups.com
Dear Victor,

As the message says, you should install yacc. That's probably easier
than the workaround.

Yacc is really only needed to build the dependency generation tool. The
workaround is therefore to bypass the dependency generation tool by
getting the dependency files elsewhere. This might work:
1. Get the dependency files from the same CP2K version on any
machine with the same build definitions. They are the *.dep
files in the obj/$ARCH/$VERSION directory.
2. Start your build and wait for it to fail.
3. Clean up the mis-built directory with the "clean" make target.
4. Copy the dependency files from step 1 into the new
obj/$ARCH/$VERSION directory and "touch" them to make them have
a new date.

Cheers.
> --
> You received this message because you are subscribed to the Google
> Groups "cp2k" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to cp2k+uns...@googlegroups.com.
> To post to this group, send email to cp...@googlegroups.com.
> Visit this group at http://groups.google.com/group/cp2k?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


Michael Banck

unread,
May 15, 2013, 5:21:07 AM5/15/13
to cp...@googlegroups.com
Hi,

On Wed, May 15, 2013 at 09:31:33AM +0200, Urban Borštnik wrote:
> As the message says, you should install yacc. That's probably easier
> than the workaround.

It is customary to not require lex/yacc for release tarballs (same for
autoconf etc. usually), only when building from the development source
repository.

I.e. it would be nice to include those files in the next release tarball
for easier installation by users.


Michael
Reply all
Reply to author
Forward
0 new messages