configure command line in installed directories?

Ralf Corsepius ralf.corsepius at
Mon Apr 14 04:41:42 UTC 2008

On Sun, 2008-04-13 at 16:42 +0200, Thomas Doerfler wrote:
> Hi Ralf,
> Ralf Corsepius schrieb:
> > On Sat, 2008-04-12 at 09:36 +0200, Thomas Doerfler wrote:
> >> Hi,
> >>
> >> Robert Grimes had the question, how he can find out the "configure" 
> >> command line, that was used to build RTEMS. We could help him. AFAIK the 
> >> relevant information can be retrieved from some files inside the build 
> >> directory, but:
> >>
> >> It can't be determined from the installed files.
> > Correct.
> > 
> >> Wouldn't it be nice to have that information written to one of the 
> >> installed files?
> > No.
> Could you be a bit more specific?
Recording and hard-coding configure-arguments is a silly idea, because
configure-arguments only have a meaning to a local source tree.

They are meaningless to anything outside of the particular sources,
because a library package (such as RTEMS) has no knowledge about what
infrastructure users might be using.

>  If you think about a team working with 
>   an installed version of RTEMS, for a given project, I regard it 
> preferable that everybody can find out how RTEMS has been configured.
No - Nobody needs this kind of information.

What people need is information on "features a package has built-in".

> And AFAIK the build directory is a temporary one, so in general it can 
> be removed after the built files have been installed.
Correct, it's temporary and so are configure-arguments - They should not
be of interest to anybody.


More information about the users mailing list