ghost/test/multitest fails to build #37187

New Issue

Lawrence D'Oliveiro · 2013-10-23T08:37:05+02:00

2013-10-23 08:37:05 +02:00

%%%The “multitest” test program for GHOST fails to link with a pair of undefined-symbol errors (BLI_task_scheduler_free among them). On investigation, definitions of these symbols were found in source/blender/blenlib/intern/task.c. This file was omitted from the ”add_library(bli_lib” call in intern/ghost/test/CMakeLists.txt. Including it causes the build to succeed. The enclosed patch adds this file.%%%

Lawrence D'Oliveiro commented

2013-10-23 08:37:05 +02:00

Changed status to: 'Open'

Sergey Sharybin commented

2013-10-28 13:54:50 +01:00

%%%Commited the patch at svn rev60966. Thanks for it.

In the future please do not use this bug tracker to report compilation issues and use ML or IRC room instead! This is the rule #1 in report bug guidelines which you scrolled through when was reporting the issue.%%%

%%%Commited the patch at svn rev60966. Thanks for it. In the future please do not use this bug tracker to report compilation issues and use ML or IRC room instead! This is the rule #1 in report bug guidelines which you scrolled through when was reporting the issue.%%%

Sergey Sharybin commented

2013-10-28 13:54:50 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2013-10-28 13:54:50 +01:00

Lawrence D'Oliveiro commented

2013-10-28 23:42:54 +01:00

%%%What is a bug? It is something wrong with the program. Whether it doesn’t run right, or doesn’t build right, or a user message isn’t spelled right, these are all bugs.

Why do we use a bug tracker? So that we have a central record of the fact that a) a bug was reported, b) additional information was/was not requested/supplied, and c) action was/was not taken to fix it.

Note that word CENTRAL. It means someone else encountering the same bug doesn’t have to go searching through random mailing list archives or IRC logs to discover that something similar has already been reported and discussed at length elsewhere.

Now, I freely admit your bug tracker is crap. I still cannot figure out how to search through previous bug reports to find out if the same bug was already reported and closed wontfix/invalid/todo, that kind of thing. But as crap as it is, it is better than nothing. And as long as it is better than nothing, I will continue to use it.

If it’s a bug, and it has to do with the main Blender source tree, it goes in this bug tracker. Is that understood?
%%%

%%%What is a bug? It is something wrong with the program. Whether it doesn’t run right, or doesn’t build right, or a user message isn’t spelled right, these are all bugs. Why do we use a bug tracker? So that we have a central record of the fact that a) a bug was reported, b) additional information was/was not requested/supplied, and c) action was/was not taken to fix it. Note that word CENTRAL. It means someone else encountering the same bug doesn’t have to go searching through random mailing list archives or IRC logs to discover that something similar has already been reported and discussed at length elsewhere. Now, I freely admit your bug tracker is crap. I still cannot figure out how to search through previous bug reports to find out if the same bug was already reported and closed wontfix/invalid/todo, that kind of thing. But as crap as it is, it is better than nothing. And as long as it is better than nothing, I will continue to use it. If it’s a bug, and it has to do with the main Blender source tree, it goes in this bug tracker. Is that understood? %%%

Sergey Sharybin commented

2013-10-29 10:53:36 +01:00

%%%I think first paragraph of report bug guidelines answers your question explicitly: This bug tracker is for end-user issues with Blender binaries

It is just unefficient to use the bug tracker to report compilation errors. Source tree might become broken for compilation on different platforms ten time per day. Reporting all of them will clutter the bug tracker. Also, reporting compilation issues to the ML/IRC will give you more instant reply.

For more information please read bug report guidelines: https://projects.blender.org/tracker/?func=add&group_id=9&atid=498%%%

%%%I think first paragraph of report bug guidelines answers your question explicitly: This bug tracker is for end-user issues with Blender binaries It is just unefficient to use the bug tracker to report compilation errors. Source tree might become broken for compilation on different platforms ten time per day. Reporting all of them will clutter the bug tracker. Also, reporting compilation issues to the ML/IRC will give you more instant reply. For more information please read bug report guidelines: https://projects.blender.org/tracker/?func=add&group_id=9&atid=498%%%

Lawrence D'Oliveiro commented

2013-10-29 22:31:25 +01:00

%%%OK, I can see why that could be a problem. Except this bug I reported wasn’t something that occurs “ten times per day”—it was obviously older than that.

My own personal guideline is, I do not make a commit unless I am sure the code still builds.%%%

%%%OK, I can see why that could be a problem. Except this bug I reported wasn’t something that occurs “ten times per day”—it was obviously older than that. My own personal guideline is, I do not make a commit unless I am sure the code still builds.%%%

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

ghost/test/multitest fails to build #37187