Re: Build scripts bugs (9.2.0.p01)

Help: Forums, postings and threads

Forums, postings and threads

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.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

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.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
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.

Argument Default value Alternative Comment

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)

Argument	Default value	Alternative	Comment
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)

Hi Olivier,

Thanks for the feedback!

On Mon, 17 Aug 2009 09:24:52 GMT, Olivier LAHAYE wrote:
> 1) If you select build with Qt and choose /usr/lib64/qt4 as QTDIR, the
> moc program is /usr/bin/moc (a 3.3 version) instead of $QTDIR/bin/moc
> (/usr/lib64/qt4/bin/moc)

This is already fixed in CVS, where an extra check is done to confirm that the detected moc matches the detected Qt install.

> 2) There is no way to select a paralell build (make -j12). I need to
> edit the /config/...../config.sh file

I've been putting together a Configure-generated top level Makefile that should resolve this (giving you a potential Configure/make/make install solution). It is still a work in progress though...

> 3) 64bit is not handeled correctly. libdir name is hardcoded to lib
> instead of lib64 on 64bits systems. This prevents to install geant4 as a
> system wide application (typicaly from a rpm package).

Do you mean lib is hardcoded in the checks that Configure does, or the directories where the geant4 libraries are installed?

> 4) Configure script fails to recreate a config from a config.sh file. In
> fact, many variables are missed, resulting in a bad config. ./Configure
> -der -f config.sh -E If you do a diff between this config.sh and
> .config/bin/Linux-g++/config.sh you'kll see that many variable are using
> default values instead of values from config.sh

Right, that's probably due to some incorrect logic in the handling of default values. I'll take a look.

> 5) install.sh and move.sh have missleading names. install.sh should be
> renamed build.sh move.sh should be renamed install.sh

Agreed, we'll see about changing these, or using the top-level Makefile solution.

> 6) if copy all includes in one directory is selected, then the make
> include in not triggered by default.

A Configure -install after the Configure -build usually handles this. Otherwise, if you're running direct with the Makefiles, gmake includes in the source directory should work. I may have misunderstood what you mean by 'not triggered by default' though?

> 7) No way to set XERCESCROOT from Configure script.

I'm not sure what you mean here - running interactively, Configure will automatically check for Xerces-c, and then query the user for XERCESCROOT if it doesn't find it. One can force the value via the variables

g4lib_build_gdml

g4gdml_xercesc_root




which you can set in your input config.sh, or at the command line with -D options.


> 8) No way to install geant4 as a system wide app like: /usr/bin (for
> binaries) /usr/lib64/geant4 (for libraries) /usr/include/geant4 (for
> includes) /usr/share/geant4/config (for config) /usr/share/geant4/data
> (for data) Instead (enventhough I said that I want to build only for one
> architecture), I'm force to have my libs and binaries in a sub directory
> named Linux-g++ which is more than ugly when you install a system wide
> application.



I'll take a look at fixing this!


> Please concider using autotools or cmake as build system as the current
> one is buggy and difficult to maintain (IMHO).



The collaboration is working on a replacement build system using standard cross-platform tools - we're aware of the issues with the current system... - and it's a work in progress at this point!



Cheers,



Ben