Re: [Tigervnc-devel] External dependencies in cross-compatible build
Brian, Just tried to use the Mac viewer build on 10.6. I get immediate crashes. Below is the otool library list for reference. Robert otool -L /Applications/TigerVNC\ Viewer\ 1.2.90.app/Contents/MacOS/TigerVNC\ Viewer /Applications/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer: /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 17.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 153.0.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 41.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libpam.2.dylib (compatibility version 3.0.0, current version 3.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 635.21.0) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 53.0.0) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1138.51.0) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 833.25.0) On Sat, May 18, 2013 at 6:29 PM, Brian Hinz bph...@users.sourceforge.netwrote: On Fri, May 17, 2013 at 2:30 PM, DRC dcomman...@users.sourceforge.netwrote: Brian, While we're on the subject, the Mac build has similar issues. It won't run on Mountain Lion: dyld: Library not loaded: /usr/local/lib/libintl.8.dylib Referenced from: /Applications/Network/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer Reason: image not found When I was maintaining the builds, I had to build both GnuTLS and gettext from source on Mac in order to make that build cross-compatible. I just uploaded a new Mac build linked against a static libintl. If someone could test it on Mountain Lion I'd appreciate it, I only have access to 10.7 Lion. Thanks, -brian -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
On Wed, 22 May 2013 09:08:30 -0400 Robert Goley rago...@rdasys.com wrote: Brian, Just tried to use the Mac viewer build on 10.6. I get immediate crashes. Below is the otool library list for reference. In case it helps, this is the link line CMake generates in my hacked up working copy: /usr/bin/i686-apple-darwin8-c++ -O3 -DNDEBUG -headerpad_max_install_names CMakeFiles/vncviewer.dir/buildTime.cxx.o CMakeFiles/vncviewer.dir/menukey.cxx.o CMakeFiles/vncviewer.dir/CConn.cxx.o CMakeFiles/vncviewer.dir/DesktopWindow.cxx.o CMakeFiles/vncviewer.dir/UserDialog.cxx.o CMakeFiles/vncviewer.dir/ServerDialog.cxx.o CMakeFiles/vncviewer.dir/OptionsDialog.cxx.o CMakeFiles/vncviewer.dir/Viewport.cxx.o CMakeFiles/vncviewer.dir/parameters.cxx.o CMakeFiles/vncviewer.dir/keysym2ucs.c.o CMakeFiles/vncviewer.dir/vncviewer.cxx.o CMakeFiles/vncviewer.dir/cocoa.mm.o CMakeFiles/vncviewer.dir/OSXPixelBuffer.cxx.o -o vncviewer -nodefaultlibs ../common/rfb/librfb.a ../common/network/libnetwork.a ../common/rdr/librdr.a ../common/os/libos.a ../common/Xregion/libXregion.a -framework Carbon -framework Cocoa -framework ApplicationServices -Wl,-Bstatic -lfltk -Wl,-Bdynamic -Wl,-Bstatic -lintl -liconv -Wl,-Bdynamic -liconv -Wl,-Bstatic -lstdc++ -Wl,-Bdynamic -lc -lgcc -lgcc_eh -Wl,-Bstatic -ljpeg -lz -Wl,-Bdynamic -lgcc Rgds -- Pierre Ossman Software Development Cendio AB http://cendio.com Teknikringen 8 http://twitter.com/ThinLinc 583 30 Linköpinghttp://facebook.com/ThinLinc Phone: +46-13-214600http://plus.google.com/112509906846170010689 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
The May 18 cross-compatible build fits perfectly on Xubuntu 12.04: extra libraries are no longer necessary. However, the 1.9 MB savings from no longer needing to add libcrypto.so.6 and libgnutls.so.13 are more than paid for by the 4.2 MB increase of the executables. And retrieving some extra libraries is a nobrainer thanks to RPM Search ... I also tested the May 18 cross-compatible build on Slackware Current: the only additional libraries required are libpam.so.0 and libpam_misc.so.0. Slackware provides libpam in an extra package, but not libpam_misc. Luckily compiling Linux-PAM-1.1.6 from source is a nobrainer too. As I said before, a complete tigervnc build from source on Slackware was successful and did not require foreign libraries. Regards, Dick -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
On Fri, May 17, 2013 at 2:30 PM, DRC dcomman...@users.sourceforge.netwrote: Brian, While we're on the subject, the Mac build has similar issues. It won't run on Mountain Lion: dyld: Library not loaded: /usr/local/lib/libintl.8.dylib Referenced from: /Applications/Network/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer Reason: image not found When I was maintaining the builds, I had to build both GnuTLS and gettext from source on Mac in order to make that build cross-compatible. I just uploaded a new Mac build linked against a static libintl. If someone could test it on Mountain Lion I'd appreciate it, I only have access to 10.7 Lion. Thanks, -brian -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
I have mountain lion. I will test it later and report back. Robert On May 18, 2013 6:29 PM, Brian Hinz bph...@users.sourceforge.net wrote: On Fri, May 17, 2013 at 2:30 PM, DRC dcomman...@users.sourceforge.netwrote: Brian, While we're on the subject, the Mac build has similar issues. It won't run on Mountain Lion: dyld: Library not loaded: /usr/local/lib/libintl.8.dylib Referenced from: /Applications/Network/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer Reason: image not found When I was maintaining the builds, I had to build both GnuTLS and gettext from source on Mac in order to make that build cross-compatible. I just uploaded a new Mac build linked against a static libintl. If someone could test it on Mountain Lion I'd appreciate it, I only have access to 10.7 Lion. Thanks, -brian -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
Brian, I tested the build on 10.8. It seems to be working fine. My test was against a 1.2 Xvnc server. I listed out the dynamic libraries it is using on 10.8 with tool. This is what I got. TigerVNC Viewer: /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 17.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 153.0.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 41.0.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libpam.2.dylib (compatibility version 3.0.0, current version 3.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 635.21.0) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 53.0.0) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1138.51.0) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 833.25.0) On Sat, May 18, 2013 at 6:29 PM, Brian Hinz bph...@users.sourceforge.netwrote: On Fri, May 17, 2013 at 2:30 PM, DRC dcomman...@users.sourceforge.netwrote: Brian, While we're on the subject, the Mac build has similar issues. It won't run on Mountain Lion: dyld: Library not loaded: /usr/local/lib/libintl.8.dylib Referenced from: /Applications/Network/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer Reason: image not found When I was maintaining the builds, I had to build both GnuTLS and gettext from source on Mac in order to make that build cross-compatible. I just uploaded a new Mac build linked against a static libintl. If someone could test it on Mountain Lion I'd appreciate it, I only have access to 10.7 Lion. Thanks, -brian -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
[Tigervnc-devel] External dependencies in cross-compatible build
Pursuant to our discussion on tigervnc-users regarding whether the project RPMs could be used on SuSE, I noticed that the RHEL 5 RPMs and the cross-compatible build have external dependencies on GnuTLS and libstdc++. That prevents them from truly being cross-compatible. It should be possible to link statically with GnuTLS on the RHEL 5 builds, since RHEL 5 provides static library versions of GnuTLS. I'm confused as to why the libstdc++ dependency is there, since build-xorg is supposed to take care of that automatically. TigerVNC 1.2 Xvnc dependencies: linux-vdso.so.1 = (0x7fffbaba2000) libpam.so.0 = /lib64/libpam.so.0 (0x003b2fe0) libdl.so.2 = /lib64/libdl.so.2 (0x003b2be0) librt.so.1 = /lib64/librt.so.1 (0x003b3120) libm.so.6 = /lib64/libm.so.6 (0x003b2ba0) libc.so.6 = /lib64/libc.so.6 (0x003b2b60) libpthread.so.0 = /lib64/libpthread.so.0 (0x003b2c60) libaudit.so.0 = /lib64/libaudit.so.0 (0x003b2de0) /lib64/ld-linux-x86-64.so.2 (0x003b2b20) TigerVNC 1.3 Xvnc dependencies: linux-vdso.so.1 = (0x7fffc8569000) libgnutls.so.13 = /usr/lib64/libgnutls.so.13 (0x003b3f40) libz.so.1 = /lib64/libz.so.1 (0x003b2c20) libpam_misc.so.0 = /lib64/libpam_misc.so.0 (0x003b2da0) libpam.so.0 = /lib64/libpam.so.0 (0x003b2fe0) libcrypto.so.6 = /lib64/libcrypto.so.6 (0x003b3420) libdl.so.2 = /lib64/libdl.so.2 (0x003b2be0) librt.so.1 = /lib64/librt.so.1 (0x003b3120) libstdc++.so.6 = /usr/lib64/libstdc++.so.6 (0x2b4b6762) libm.so.6 = /lib64/libm.so.6 (0x003b2ba0) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x003b2de0) libc.so.6 = /lib64/libc.so.6 (0x003b2b60) /lib64/ld-linux-x86-64.so.2 (0x003b2b20) libgcrypt.so.11 = /usr/lib64/libgcrypt.so.11 (0x003b4100) libgpg-error.so.0 = /usr/lib64/libgpg-error.so.0 (0x003b4140) libaudit.so.0 = /lib64/libaudit.so.0 (0x2b4b67922000) libpthread.so.0 = /lib64/libpthread.so.0 (0x003b2c60) -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
On Fri, May 17, 2013 at 2:06 PM, DRC dcomman...@users.sourceforge.netwrote: Pursuant to our discussion on tigervnc-users regarding whether the project RPMs could be used on SuSE, I noticed that the RHEL 5 RPMs and the cross-compatible build have external dependencies on GnuTLS and libstdc++. That prevents them from truly being cross-compatible. It should be possible to link statically with GnuTLS on the RHEL 5 builds, since RHEL 5 provides static library versions of GnuTLS. I'm confused I thought that was the case as well, thanks for catching this. I'll review the RPM tonight. (same for libstdc++) On a related note, I have not been able to build against even relatively new versions of GNUTLS because of some ifdef statements in our code and changes in their API. I was working on a patch last week that I'll run by the list later tonight as well. -brian -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
On Fri, May 17, 2013 at 2:30 PM, DRC dcomman...@users.sourceforge.netwrote: Brian, While we're on the subject, the Mac build has similar issues. It won't run on Mountain Lion: dyld: Library not loaded: /usr/local/lib/libintl.8.dylib Referenced from: /Applications/Network/TigerVNC Viewer 1.2.90.app/Contents/MacOS/TigerVNC Viewer Reason: image not found When I was maintaining the builds, I had to build both GnuTLS and gettext from source on Mac in order to make that build cross-compatible. Also, I'm curious as to how you managed to avoid the libstdc++ dependency on Windows. I can only do that by patching FLTK with the same BUILD_STATIC macro that exists in the TigerVNC source. I think I'm actually using a patch that you posted to the list sometime in Februaury(?). I wasn't able to build GnuTLS correctly on MinGW so I'm linking against the pre-compiled version listed in BUILDING.txt -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
On 5/17/13 2:01 PM, Brian Hinz wrote: I think I'm actually using a patch that you posted to the list sometime in Februaury(?). I wasn't able to build GnuTLS correctly on MinGW so I'm linking against the pre-compiled version listed in BUILDING.txt Ah. OK, that's what I'm doing as well. Just checking. Yeah, I was never able to build GnuTLS on Windows either and ended up using the same pre-compiled version, which meant that I could only supply a TLS-enabled build for Win32. The Win64 build never had GnuTLS support. -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] External dependencies in cross-compatible build
Actually building 1.2.90 for Slackware current turned out not to be a terrible pain at all - after translating the RPM spec file into a bash script things went smoothly. Using this build script on Xubuntu 12.04 was ok too. But alas Xvnc there bailed out on start because of a keymap compile error or something. Using the cross compatible build was successful - I only had to extract libcrypto.so.6 and libgnutls.so.13 from the Fedora RPMs I found via RPM Search. Regards, Dick -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel