compiling conglomerate

> Make it compile; that's all I request.

It is good to report that you can't compile
the Free software you are curious about.
Writing a good report is something different.
This about how to do that. It all boils down to

  Tell what _you_ see and do at your end of the line


Realize that the people who can help you, have a working setup.
They know that telling "it works for me" doesn't solve your problem,
but it states that it could work for you also.



* Tell about your computer programs.
What operating system are you using?
And other things that you think that is different at your side.


* Version of the software
Tell the people you are asking, which release of the package are you
trying to compile. That will be a tarball ( .tar.gz ) version number.
Mention also from where you got it ( URL of the website / ftpsite )

When you are compiling from a versioning system, like subversion or cvs,
tell the date of the checkout.

If you use both, versioning and tarball, tell how you made the tarball.



* used commands to compile
most likely "make", but please tell more, even if it is only

  ./configure --prefix=/usr
  make

then tell so.


* warnings and errors that you get

Where the previous questions only provide a few lines of answers,
has this questions the risk to get many many many lines.
So before you through a complete log to your co-workers,
spend some time on it in cleaning it up, in making summaries.
While doing that you might even find the reason why it doesn't compile.


* post the report

Please do more then just clicking on 'send message'.
Check the "it fails to build from source report" again.
Repair type errors, remove redundant lines, re-order in a logical order.


* Handle the feedback with respect

It is hard to tell what the answer is that you will recieve,
but no matter what, stay calm and reply on a constructive base.

In case you got a "Oops, didn't known it was broken, now fixed"
then try it and confirm that it works, show that you care.

In case you got a request for more detailed information,
then provide it. When you allow yourself much time to supply that
information, then the other end knows there is no need to hurry.
Show that you care.


* When you don't get feedback

Then it could be that you are not aware of
 http://www.catb.org/~esr/faqs/smart-questions.html
so read that nice writing.

To solve the compile error, you have to try again.
I mean on your side, not simply reposting.
Report your progress to the people you where asking for help.
If you have didn't make progress, then tell so.
Ask what a working setup is.


Cheers
Geert Stappers

_______________________________________________
Conglomerate-devel mailing list
[email protected]
http://lists.copyleft.no/mailman/listinfo/conglomerate-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCffynOSINbgwa/7sRAtXKAKChmSR95/8E9LkIxj6hDnladuRP1wCgn8bH
FhazEvCPsB9hsnHmRhlUHQQ=
=K/A9
-----END PGP SIGNATURE-----