|
[Sponsors] |
[foam-extend.org] Error compiling OpenFOAM-1.6-ext |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
November 30, 2010, 10:50 |
|
#21 | |
Senior Member
Daniel WEI (老魏)
Join Date: Mar 2009
Location: Beijing, China
Posts: 689
Blog Entries: 9
Rep Power: 21 |
Quote:
__________________
~ Daniel WEI ------------- Boeing Research & Technology - China Beijing, China |
||
November 30, 2010, 17:26 |
|
#22 |
Senior Member
David Boger
Join Date: Mar 2009
Location: Penn State Applied Research Laboratory
Posts: 146
Rep Power: 17 |
I was able to pull the correction in commit 4fcfce1 (thanks Martin and Philippose), but a subsequent top-level Allwmake still leaves me with "no such file" errors on MsqIMesh.hpp, MsqIGeom.hpp, and MsqIRel.hpp. Is there something I need to do to "clean out" mesquite-2.1.2 in order for the correction to have an effect?
Ah - in retrospect, I see that the configure is run with --disable-imesh etc., whereas --enable-imesh would be needed for the .hpp file to be installed.
__________________
David A. Boger Last edited by boger; November 30, 2010 at 17:49. |
|
November 30, 2010, 21:17 |
|
#23 |
Senior Member
Pei-Ying Hsieh
Join Date: Mar 2009
Posts: 334
Rep Power: 18 |
Hi,
I have the following errors in stage 4. How can I initialize QT-DIR? Will it fix the /bin/qmake issue too? Thanks! Pei-Ying -------------------- ======================================== Starting ThirdParty AllMake: Stage4 ======================================== WARNING: Skipping the installation of ParaView-3.8.1. WARNING: Please initialize the QT_DIR environment variable to your QT installation directory. WARNING: The command /bin/qmake needs to be valid WARNING: ======================================== Done ThirdParty AllMake: Stage4 ======================================== |
|
November 30, 2010, 21:20 |
|
#24 |
Senior Member
Daniel WEI (老魏)
Join Date: Mar 2009
Location: Beijing, China
Posts: 689
Blog Entries: 9
Rep Power: 21 |
I guess you could solve that by setting
export QT_DIR=/usr before compile paraview. But I am bot sure.
__________________
~ Daniel WEI ------------- Boeing Research & Technology - China Beijing, China |
|
November 30, 2010, 22:17 |
|
#25 | |
Senior Member
Martin Beaudoin
Join Date: Mar 2009
Posts: 332
Rep Power: 22 |
Hello Bastil,
I will contribute some modification for setting up the OF environment variables when you want to reuse your system-installed ThirdParty packages instead. You won't need any .csh/.sh files for this. Please note that this will need some additional testing before releasing, so thank you for your patience. If you are in a hurry, then you can always download the various tarballs from another machine with a working wget command, and transfer the tarballs under the directory ThirdParty/rpmBuild/SOURCES. When the compilation scripts detect that the package tarball is already available, then wget is no longer invoke. Martin Quote:
|
||
November 30, 2010, 22:21 |
|
#26 |
Senior Member
David Boger
Join Date: Mar 2009
Location: Penn State Applied Research Laboratory
Posts: 146
Rep Power: 17 |
Probably right. The error message in AllMake.stage4 actually says
Code:
echo "WARNING: The command $QT_DIR/bin/qmake needs to be valid"
__________________
David A. Boger |
|
November 30, 2010, 22:30 |
|
#27 | |
Senior Member
Martin Beaudoin
Join Date: Mar 2009
Posts: 332
Rep Power: 22 |
Hello David,
This is a nagging little problem. I though we nailed it down properly with the fix contributed by Philippose, but it looks like we need to revisit this one yet again. Basically, all the configuration parameters for compiling Mesquite were recommended by Sandeep Menon, so I basically applied the same recipe. I don't mind changing the configure parameters as long as the compiled mesquite library is still usable by OF-1.6-ext. I will contact Sandeep in order to get some advices over this one. In the meantime, would you mind telling me on what platform/OS you are experiencing this problem? I am having a very hard time replicating this problem, and I am using 6 different Unix flavours for testing the new ThirdParty packages setup, to no avail... Thank you for your input! Martin Quote:
|
||
November 30, 2010, 22:30 |
|
#28 | |
Senior Member
Martin Beaudoin
Join Date: Mar 2009
Posts: 332
Rep Power: 22 |
Yup, noted.
Thanks! Martin Quote:
|
||
November 30, 2010, 22:38 |
|
#29 |
Senior Member
Daniel WEI (老魏)
Join Date: Mar 2009
Location: Beijing, China
Posts: 689
Blog Entries: 9
Rep Power: 21 |
And, I mean no discouragement, I love the rpm idea too, it works very well in my laptop, and personal workstation, but since I met problems in installing the packages in our campus' high performance computer using rpm, which then makes me think, that whether rpm is a good idea for a "general" installation.
I advice that another way be simultaneously provided or kept, that is the way simply through something like Allwmake as in old Thirdparty dir. For not all the hardware setting is very suitable for rpm. We should give users more flexibility to install the packages more "manually". And also I found the new scotch compilation is little tricky in some computer architecture, the Makefile.inc just doesn't work very well.
__________________
~ Daniel WEI ------------- Boeing Research & Technology - China Beijing, China |
|
November 30, 2010, 23:48 |
|
#30 | |
Senior Member
David Boger
Join Date: Mar 2009
Location: Penn State Applied Research Laboratory
Posts: 146
Rep Power: 17 |
I'm using OpenSUSE 11.1, so I don't know if you want to bother replicating that one! Besides, looking into it, I see now why the fix contributed by Philippose should work. I just think that having already compiled mesquite, the damage was done and that I needed to wipe out mesquite and recompile it for the correction to take effect. Short of that, removing the pesky files from the Mesquite_all_headers.hpp is probably an easier patch than copying the files from the original src as suggested above.
Quote:
__________________
David A. Boger |
||
December 1, 2010, 00:31 |
|
#31 |
Senior Member
David Boger
Join Date: Mar 2009
Location: Penn State Applied Research Laboratory
Posts: 146
Rep Power: 17 |
And sure enough, Martin, of course you were right. With the latest commits, once I deleted mesquite from the packages and RPMs directories and re-ran the AllMake.stage3, all was well with the mesquite header files. Sorry for getting you off on a wild goose chase!
__________________
David A. Boger |
|
December 1, 2010, 00:45 |
|
#32 | |
Senior Member
Martin Beaudoin
Join Date: Mar 2009
Posts: 332
Rep Power: 22 |
Good news! Looks like we can put that one to rest.
Martin Quote:
|
||
December 1, 2010, 04:49 |
Compilation in SP
|
#33 |
Senior Member
BastiL
Join Date: Mar 2009
Posts: 530
Rep Power: 20 |
I ran into a problem with compiling 1.6-ext in SP. Where can I report a bug - it is not yet in the Bug-tracker?
Regards Bastian |
|
December 1, 2010, 08:49 |
compile ThirdParty packages
|
#34 |
Senior Member
Pei-Ying Hsieh
Join Date: Mar 2009
Posts: 334
Rep Power: 18 |
Hi,
I have a much simpler issue and will appreciate if someone here can help. I have a computer that is not connected to the internet. When I issued the AllMake command in ThridParty, it looks like the script tried to download the source codes of the packages from the internet, and of course, failed. I can download all the packages manually from another computer which has access to internet, but, where do I put the source codes? Will the AllMake script knows where to find these packages without going to internet? Pei |
|
December 1, 2010, 09:16 |
|
#35 |
Senior Member
David Boger
Join Date: Mar 2009
Location: Penn State Applied Research Laboratory
Posts: 146
Rep Power: 17 |
Look in ThirdParty/tools/makeThirdPartyFunctionsForRPM. On line 78, it checks first to see whether the "packageTarBall" is in the SOURCES directory (assuming it has not already found the rpm file).
__________________
David A. Boger |
|
December 1, 2010, 13:08 |
|
#36 |
Senior Member
Pei-Ying Hsieh
Join Date: Mar 2009
Posts: 334
Rep Power: 18 |
Thanks a lot David and Daniel!
After seeting QT_DIR=/usr, paraview compiled, but, I got several link errors. Do I have to long in as root or use sudo? Pei-Ying --------------------- + echo 'Generating OpenFOAM specific .csh and .sh files for the package ParaView-3.8.1' Generating OpenFOAM specific .csh and .sh files for the package ParaView-3.8.1 + echo '' + mkdir -p /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILDROOT/ParaView-3.8.1-linux64GccDPOpt.x86_64//home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/etc + cat + cat + /usr/lib/rpm/brp-lib64-linux sf@suse.de: if you find problems with this script, drop me a note + RPM_BUILD_ROOT=/home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILDROOT/ParaView-3.8.1-linux64GccDPOpt.x86_64 + export RPM_BUILD_ROOT + test -x /usr/sbin/Check -a 1001 = 0 -o -x /usr/sbin/Check -a '!' -z /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILDROOT/ParaView-3.8.1-linux64GccDPOpt.x86_64 + echo 'I call /usr/sbin/Check...' I call /usr/sbin/Check... + /usr/sbin/Check Checking permissions and ownerships - using the permissions files /tmp/Check.perms.j0x42f setting /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILDROOT/ParaView-3.8.1-linux64GccDPOpt.x86_64/ to root:root 0755. (wrong owner/group hsieh:users) setting /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILDROOT/ParaView-3.8.1-linux64GccDPOpt.x86_64/home/ to root:root 0755. (wrong owner/group hsieh:users) + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-symlink ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/qt4/lib -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/lib64 Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/qt4/include -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/include Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/qt4/bin -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/bin Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/qt3 -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/lib/qt3 Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/xulrunner-devel-1.9.1.13/include -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/include/xulrunner-1.9.1.13/unstable Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/xulrunner-devel-1.9.1.13/idl -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/include/xulrunner-1.9.1.13/unstable Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/xulrunner-devel-1.9.1.13/sdk/include -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/include/xulrunner-1.9.1.13/stable Add the package providing the target to neededforbuild and Requires ERROR: link target doesn't exist (neither in build root nor in installed system): /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/xulrunner-devel-1.9.1.13/sdk/idl -> /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/include/xulrunner-1.9.1.13/stable Add the package providing the target to neededforbuild and Requires INFO: relinking /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/packages/ParaView-3.8.1/platforms/linux64GccDPOpt/lib/paraview-3.8/ooo3/share/uno_packages/cache/uno_packages/oacnGn_/mysql-connector-ooo.oxt -> /usr/lib64/ooo3/share/extension/install/mysql-connector-ooo.oxt (was /usr/lib64/ooo3/share/extension/install/mysql-connector-ooo.oxt/) error: Bad exit status from /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/tmp/rpm-tmp.v6e24b (%install) RPM build errors: Bad exit status from /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/tmp/rpm-tmp.v6e24b (%install) Installing package: ParaView-3.8.1 Uninstalling ParaView-3.8.1 using RPM: ParaView-3.8.1-linux64GccDPOpt.x86_64 Installing ParaView-3.8.1 using RPM file: /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-3.8.1-linux64GccDPOpt.x86_64.rpm error: open of /home/hsieh/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-3.8.1-linux64GccDPOpt.x86_64.rpm failed: No such file or directory Done installing package ParaView-3.8.1 ======================================== Done ThirdParty AllMake: Stage4 ======================================== ======================================== Done ThirdParty Allwmake ======================================== |
|
December 1, 2010, 23:13 |
|
#37 | |
Senior Member
Martin Beaudoin
Join Date: Mar 2009
Posts: 332
Rep Power: 22 |
Hello,
Some important information is missing here: What platform/OS are you using? What is the version of QT installed on your machine? Martin Quote:
|
||
December 2, 2010, 08:50 |
|
#38 |
Senior Member
Pei-Ying Hsieh
Join Date: Mar 2009
Posts: 334
Rep Power: 18 |
Hi, Martin,
I am using OpenSUSE 11.3 64 bit OS. AMD Phenom II 955 CPU. I believe that my QT version is 4.6.3-2.1.1 Thanks! Pei-Ying |
|
December 3, 2010, 01:47 |
|
#39 |
New Member
Norbert Vogl
Join Date: Mar 2009
Posts: 2
Rep Power: 0 |
Hello,
I found the same behavior also on OpenSUSE 11.3 64 bit. It seems that the rpm procedure copies a lot of files from the /usr/lib directory to the rpm installation directory. (I found there a copy of yast2!) Norbert |
|
December 3, 2010, 05:58 |
|
#40 |
Member
|
I also got same error message on SUSE both for 11.2 and 11.3.
My Qt are respectively 4.5.3 and 4.6.3.
__________________
Cosimo Bianchini Ergon Research s.r.l. Via Panciatichi, 92 50127 Florence - ITALY Tel: +39 055 0763716 Mob: +39 320 9460153 e-mail: cosimo.bianchini@ergonresearch.it URL: www.ergonresearch.it |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Frequently Asked Questions about Installing OpenFOAM | wyldckat | OpenFOAM Installation | 3 | November 14, 2023 12:58 |
OpenFOAM Training, London, Chicago, Munich, Houston 2016-2017 | cfd.direct | OpenFOAM Announcements from Other Sources | 0 | September 14, 2016 04:19 |
New OpenFOAM Forum Structure | jola | OpenFOAM | 2 | October 19, 2011 07:55 |
OpenFOAM 1.6 package - CentOS 5.3 x86_64 | linnemann | OpenFOAM Installation | 36 | September 2, 2009 13:46 |
OpenFOAM Version 1.6 Released | opencfd | OpenFOAM Announcements from ESI-OpenCFD | 0 | July 27, 2009 18:55 |