By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1138 - Build issue: tdenetwork does not support parallel build
Summary: Build issue: tdenetwork does not support parallel build
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdenetwork (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: All Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-08-02 02:55 CDT by Francois Andriot
Modified: 2013-11-24 23:49 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Andriot 2012-08-02 02:55:51 CDT 
Hello, when building tdeneworks with "make -jX" where X>1 , it always fails with strange errors. I've already applied commit #35c41f35  from GIT.

It looks like we still have to compile it without parallel build for now.
Comment 1 Darrell 2012-10-17 19:55:07 CDT 
Does this bug still exist? I have been building tdenetwork GIT with -j4 for a few months now.
Comment 2 Francois Andriot 2012-10-17 23:53:38 CDT 
Yes, it still happens sometimes.
I just have to try again and it generally goes well the second try.

I'm using -j10 .
Comment 3 Darrell 2012-10-18 14:50:21 CDT 
I'm discovering that tdenetwork is messed up bad, both with cmake and autotools. I'm going to post some patches in bug report 1040. I posted one patch in bug report 1274. Possibly after patching parallel builds will work for everybody.
Comment 4 Darrell 2013-11-24 23:00:04 CST 
Is this report still valid? I have been building tdenetwork with cmake for many months using -j4.
Comment 5 Francois Andriot 2013-11-24 23:49:56 CST 
No, it works as expected now.