On Thu, 20 Mar 2014 17:25:15 kcrisman wrote: > On Thursday, March 20, 2014 5:11:23 PM UTC-4, Jean-Pierre Flori wrote: > > On Thursday, March 20, 2014 9:44:57 PM UTC+1, François wrote: > >> I think I am starting to get some ideas. The missing includes are an > >> essential > >> key to understand the problem. We may need the result of the > >> configuration > >> phase on that machine. The includes statements are present in the > >> following > >> form > >> -include $(patsubst %, %.d, $(PROFS)) > >> with variations, this is just the first one in Makefile.subdirs. > >> The "-" means the process will continue even if it doesn't find a file. > >> The message are generated when you don't find a file to include. > >> Possibilities: > >> *make is too old and doesn't support the syntax in the include line > >> *some variables in the include line are not defined. We need the > >> configuration > >> to get that. > >> > >> FYI, the configuration basically only spits things into the Makefile, so > > > > we would need the Makefile after running configure. > > You can issue "./sage -f -s flint " (and kill the build process) and get > > it in local/var/tmp/.../flint.../src/Makefile > > Thanks for this digging, everybody. I'll try this tomorrow at some point > and upload Makefile. I only have physical access (no virtual access > allowed) to this machine during limited hours M-F, sorry, though I have > another machine at home I might be able to cook something up with, you > never know...
version of make (make -v) could also be of interest. Francois -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
