Link to build log file:
http://humanreadable.nfshost.com/files/kdebase-3.5.13-i486-svn_1224113-build...
Darrell
On Tuesday 08 March 2011 06:42:54 Darrell Anderson wrote:
Link to build log file:
http://humanreadable.nfshost.com/files/kdebase-3.5.13-i486-svn_1224113-buil d.log.gz
Please use out-of-source mode, if you don't use it already.
All of my build scripts work in $TMP, outside the source tree. :)
Still can't build.
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 3:02 AM On Tuesday 08 March 2011 06:42:54 Darrell Anderson wrote:
Link to build log file:
http://humanreadable.nfshost.com/files/kdebase-3.5.13-i486-svn_1224113-buil d.log.gz
Please use out-of-source mode, if you don't use it already.
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 08 March 2011 20:39:49 Darrell Anderson wrote:
All of my build scripts work in $TMP, outside the source tree. :)
I see this:
cd /dev/shm/kdebase/kioslave/nfs && rpcgen -c -o nfs_prot_xdr.c /dev/shm/kdebase/kioslave/nfs/nfs_prot.x
This meaning that CMAKE_SOURCE_DIR is /dev/shm/kdebase/kioslave/nfs, which are the same with CMAKE_BINARY_DIR, which is /dev/shm/kdebase/kioslave/nfs as well.
Are you sure that you're out-of-source? If yes, why nfs_prot.x is in build directory?
Still can't build.
Darrell
When I build the packages, my build script copies all of the source files from my svn storage location on my hard drive to $TMP, which is located at /dev/shm (ram disk).
I do not build the packages in the svn source tree on the hard drive.
If you are saying that I cannot build the package from with the copied source files at $TMP, then I need some tutoring how to modify the build scripts accordingly. The wiki provides no such details.
The process I am using is the same one I used to successfully build all the packages under automake.
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 12:47 PM On Tuesday 08 March 2011 20:39:49 Darrell Anderson wrote:
All of my build scripts work in $TMP, outside the
source tree. :)
I see this:
cd /dev/shm/kdebase/kioslave/nfs && rpcgen -c -o nfs_prot_xdr.c /dev/shm/kdebase/kioslave/nfs/nfs_prot.x
This meaning that CMAKE_SOURCE_DIR is /dev/shm/kdebase/kioslave/nfs, which are the same with CMAKE_BINARY_DIR, which is /dev/shm/kdebase/kioslave/nfs as well.
Are you sure that you're out-of-source? If yes, why nfs_prot.x is in build directory?
Still can't build.
Darrell
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 08 March 2011 21:09:46 Darrell Anderson wrote:
When I build the packages, my build script copies all of the source files from my svn storage location on my hard drive to $TMP, which is located at /dev/shm (ram disk).
I do not build the packages in the svn source tree on the hard drive.
If you are saying that I cannot build the package from with the copied source files at $TMP, then I need some tutoring how to modify the build scripts accordingly. The wiki provides no such details.
The process I am using is the same one I used to successfully build all the packages under automake.
You using in-source mode. For out-of-source follow this example:
mkdir /dev/shm/kdebase cd /dev/shm/kdebase cmake /path/to/source [ARGUMENTS]
You don't need to copy sources to ramdisk.
Cmake will use the svn sources on my hard drive but actually build the package in $TMP?
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 1:14 PM On Tuesday 08 March 2011 21:09:46 Darrell Anderson wrote:
When I build the packages, my build script copies all
of the source files
from my svn storage location on my hard drive to $TMP,
which is located at
/dev/shm (ram disk).
I do not build the packages in the svn source tree on
the hard drive.
If you are saying that I cannot build the package from
with the copied
source files at $TMP, then I need some tutoring how to
modify the build
scripts accordingly. The wiki provides no such
details.
The process I am using is the same one I used to
successfully build all the
packages under automake.
You using in-source mode. For out-of-source follow this example:
mkdir /dev/shm/kdebase cd /dev/shm/kdebase cmake /path/to/source [ARGUMENTS]
You don't need to copy sources to ramdisk.
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Do I ever need to run 'make clean'?
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 1:32 PM On Tuesday 08 March 2011 21:28:01 Darrell Anderson wrote:
Cmake will use the svn sources on my hard drive but
actually build the
package in $TMP?
Right, this is idea.
[...]
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I updated my build scripts per your directions.
tqtinterface, arts, and kdelibs built without errors with the updated scripts.
kdebase still FTBFS with cmake, albeit much later in the script.
Link to the build log:
http://humanreadable.nfshost.com/files/kdebase-3.5.13-i486-svn_1224182-build...
Darrell
--- On Tue, 3/8/11, Darrell Anderson humanreadable@yahoo.com wrote:
From: Darrell Anderson humanreadable@yahoo.com Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 2:16 PM Do I ever need to run 'make clean'?
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 1:32 PM On Tuesday 08 March 2011 21:28:01 Darrell Anderson wrote:
Cmake will use the svn sources on my hard drive
but
actually build the
package in $TMP?
Right, this is idea.
[...]
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 08 March 2011 23:11:55 Darrell Anderson wrote:
I updated my build scripts per your directions.
tqtinterface, arts, and kdelibs built without errors with the updated scripts.
kdebase still FTBFS with cmake, albeit much later in the script.
Fixed in svn, was a parallel make problem.
Aha! :)
I just finished building kdebase with no parallel processing.
I'll update svn and try building again with parallel processing enabled.
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 3:39 PM On Tuesday 08 March 2011 23:11:55 Darrell Anderson wrote:
I updated my build scripts per your directions.
tqtinterface, arts, and kdelibs built without errors
with the updated
scripts.
kdebase still FTBFS with cmake, albeit much later in
the script.
Fixed in svn, was a parallel make problem.
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
kdebase compiles with parallel processing. :)
FWIW, kdelibs now compiles with parallel processing too, which was not the case with auotmake.
Thank you Serghei!
Darrell
--- On Tue, 3/8/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] kdebase FTBFS with cmake To: trinity-devel@lists.pearsoncomputing.net Date: Tuesday, March 8, 2011, 3:39 PM On Tuesday 08 March 2011 23:11:55 Darrell Anderson wrote:
I updated my build scripts per your directions.
tqtinterface, arts, and kdelibs built without errors
with the updated
scripts.
kdebase still FTBFS with cmake, albeit much later in
the script.
Fixed in svn, was a parallel make problem.
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Darrell Anderson -
Serghei Amelian