## cddio.c) make problem

Discussions on installation issues go here.

Moderator: Moderators

jamescussens
Posts: 5
Joined: 21 Feb 2015, 18:59

### cddio.c) make problem

Hi there,

I'm installing polymake 2.13-1 on Linux (slackware). Configure goes fine. Make proceeds well for quite some time but then crashes with the message:
make[2]: Entering directory /home/jc/local/src/polymake-2.13-1/build.Intel/staticlib/cdd'
make[3]: *** No rule to make target cddio.o)', needed by libcdd'. Stop.
make[3]: *** No rule to make target cddio.o)', needed by libcddgmp'. Stop.
make[2]: *** [compile] Error 2
make[2]: Leaving directory /home/jc/local/src/polymake-2.13-1/build.Intel/staticlib/cdd'
make[1]: *** [compile-staticlibs] Error 2
make[1]: Leaving directory /home/jc/local/src/polymake-2.13-1/build.Intel/apps/polytope'
make: *** [compile] Error 2
My guess is that the problem is the trailing parenthesis incddio.o)', but I'm not sure how to fix it.

Any help appreciated!

James

blorenz
Developer
Posts: 108
Joined: 10 Jan 2011, 17:21

### Re: cddio.c) make problem

You are correct that the parenthesis is a problem but I do not know how this could happen. What make version / variant are you using, can you post the output of the following?

Code: Select all

make -v
Additionally you could change into 'build.Intel/staticlib/cdd' and run

Code: Select all

make clean && make -p > makep.log
and upload the makep.log file, this might give an idea where the wrong make-target comes from.

Benjamin

gawrilow
Main Author
Posts: 308
Joined: 25 Dec 2010, 17:40

### Re: cddio.c) make problem

It looks like an incident in the automatic dependency generation pipeline. Either the gcc output requested by -MT looks weird, or it's a funny gmake which mis-parsed the transformation patterns. Although it might eventually be interesting to investigate the root cause, you might escape this voodoo and unblock yourself by deleting the .dependences files created below build.Intel and re-running make with an option ProcessDep=n .

gawrilow
Main Author
Posts: 308
Joined: 25 Dec 2010, 17:40

### Re: cddio.c) make problem

make -p > makep.log
make usually dumps everything to stderr, therefore 2>&1 won't harm here

jamescussens
Posts: 5
Joined: 21 Feb 2015, 18:59

### Re: cddio.c) make problem

Hi there,

Thanks for your replies. Here's the output of make -v:
GNU Make 3.82
Built for x86_64-slackware-linux-gnu
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
The output of make -p when in build.Intel/staticlib/cdd is attached. (I gave the file a .jpg extension since I got complaints about invalid file extension with its original name).

James

assarf
Developer
Posts: 74
Joined: 12 Oct 2011, 15:52

### Re: cddio.c) make problem

hmm the attachment did not come though somehow. Would you be so kind and try it again?
no signature

jamescussens
Posts: 5
Joined: 21 Feb 2015, 18:59

### Re: cddio.c) make problem

OK, sorry the attaching didn't work: using a .jpg extension led to an error (since it wasn't an image).
Since I can't get past the "invalid file extension" problem with attachments, please find the log here:

http://www-users.cs.york.ac.uk/~jc/tmp/makep.log

Thanks,
James

jamescussens
Posts: 5
Joined: 21 Feb 2015, 18:59

### Re: cddio.c) make problem

I deleted all those .dependences files (which were all empty) and tried make with ProcessDep=n, but I got the same problem.

Thanks for the suggestion anyway.

blorenz
Developer
Posts: 108
Joined: 10 Jan 2011, 17:21

### Re: cddio.c) make problem

It seems that the problem is a rather old bug in gnu make that only affects 3.8.2 (and some distributions like opensuse have this issue patched). Due to this bug the expansion of the archive members does not work properly.

To work around this bug I have attached a patch for one of the polymake Makefiles. To apply it change to the directory where you are building polymake and run:

Code: Select all

patch -p0 < /path/to/polymake_make382.patch
After this you can continue compiling polymake with 'make'.

Benjamin

PS: I had enabled the .log file extension some time ago but I somehow missed to apply this to all parts of the forum.
Attachments
polymake_make382.patch