|Message: Re: "No rule to make target" under OS X||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
An update, which may be either a clue or a workaround. I should have mentioned that, per the excellent installation instructions by Joseph Perl, I issued
export MAKEFLAGS="-j 2"
on the Core 2 Duo MacBook, and the same with "-j 8" on the quad-Xeon Nehalem (hyperthreading) Mac Pro, and I'm pretty sure I had not done this on previous installations where I didn't see this error.
So I just scrubbed the Geant4 installation (and .bashrc file) and redid the installation without the MAKEFLAGS on one of the Macs; it ran much more slowly, but in the end those error messages were not present. So I guess the multiple-thread installation set up some kind of race condition; I still don't know if the error messages indicated a temporary problem that was solved by waiting for another thread to finish, but in any case I got rid of the errors by doing the installation as a single sequence. The MAKEFLAGS suggested by Joseph Perl really did speed things up quite a lot, though, especially on my Mac Pro, so it would be good if somebody higher up the Geant4 food chain could either fix these errors or reassure us that they don't indicate more than a temporary problem. Thanks!
|Inline Depth:||Outline Depth:||Add message:|