Re: swtich back to the default (Xquartz) X11 server
On Sat, Jan 22, 2011 at 10:03 PM, Jeremy Huddleston jerem...@macports.org wrote: On Jan 22, 2011, at 01:21, iulian dragos wrote: Thanks. I managed to get xfig working by unloading the macports' agent, but dbus is still broken. Given the amount of related tickets on MacPorts trac, I am definitely not the only one seeing this. What I fail to see is a single user to actually got dbus running. I've got it running on all my machines, but I don't use nor even know what meld is... Well, the issue is not so much meld, but gconfd, which depends on dbus. It's especially frustrating, given that I don't care about configuration: Meld (http://meld.sourceforge.net/) is a graphical diff tool (the best there is). Could you give it a try? I'm sure you'll find it useful. I'm not giving up, I need to know if this works :) thanks, iulian -- « Je déteste la montagne, ça cache le paysage » Alphonse Allais ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
mingw-binutils: Segmentation fault newer version
Dear list, I'm experiencing a nasty problem with cross-compiler. I'm using 64-bit Mac OS X 10.6.6 with macports and i386-mingw32-g++ --version i386-mingw32-g++ (GCC) 3.4.5 (mingw-vista special r2) i386-mingw32-ld --version GNU ld (GNU Binutils) 2.19.1 (but I'm experiencing similar problems on another linux machine). I have reported the problem to http://lists.gnu.org/archive/html/bug-binutils/2011-01/msg00120.html and it seems that either the problem is not present in a more recent version of ld (however it is also possible that there are some architecture-specific issues). I have also submitted a bug report to mingw. But I would be very very very grateful if somebody from this mailing list could either: - explain me how exactly to compile binutils - or how to create a new port that would fetch binutils 2.21 instead of 2.19.1 and what command to execute to replace the old version with the latest one - or (even better): send me a more recent ld binary for x86_64 I have tried to download the source from https://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/GNU-Binutils/binutils-2.21/ and to compile it with ./configure --prefix='/opt/local' --infodir='/opt/local/share/info' --target=i386-mingw32 --program-prefix=i386-mingw32- --mandir='/opt/local/share/man' --disable-werror but make ended with an error gcc -DHAVE_CONFIG_H -I. -I. -I. -I../bfd -I./../bfd -I./../include -DLOCALEDIR=\/opt/local/share/locale\ -Dbin_dummy_emulation=bin_vanilla_emulation -I/opt/local/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -g -O2 -MT size.o -MD -MP -MF .deps/size.Tpo -c -o size.o size.c In file included from size.c:33: sysdep.h:30:20: error: bfdver.h: No such file or directory size.c:34:17: error: bfd.h: No such file or directory I'm not sure what flags exactly I would need in order to be able to compile binutils for macports. Any help would be highly appreciated. Thank you very much, Mojca ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Build_arch
Did you try installing libusb with the universal variant?
{sudo} port install libusb +universal
That should support multiple architectures.
Hope this helps,
Jason
On Mon, Jan 24, 2011 at 1:26 AM, Ryan Schmidt ryandes...@macports.orgwrote:
On Jan 23, 2011, at 23:11, Xander Flood wrote:
I'm running Mac OS X 10.6.4 on an Intel Core 2 Duo Macbook Pro. I'm
trying
to get libusb (for use with libfreenect to create MEX-file wrapper).
Core 2 Duo supports both the x86_64 and i386 architectures. The MATLAB
libraries I need to use are i386 (there's nothing I can do about that
short
of buying a 64-bit license all over again), but libusb is being built as
x86_64, and I obviously can't link the two together. I edited
macports.conf
to change:
build_arch = i386
but it still build an x86_64 library.
That is the correct way to request this; if it doesn't work, it is a bug in
that port.
I've run
sudo port install libusb-devel -build-arch=i386
and again the result is the same.
That doesn't do anything.
I'm not sure what to do, but is there any
way I can *actually* change the build architecture?
If setting build_arch in macports.conf does not have any effect for a
particular port, file a bug report against that port.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Graduate Student
352-392-4032
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
latexmk checksum error
Is there a work-around for the latexmk checksum error (Ticket #27863)? -Tim ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: latexmk checksum error
Hello,
Retry with verbose set:
{sudo} port -v install latexmk
You should get some message like
The correct checksum line may be:
checksums md5 12f916ba257967abea305d317c3cb840 \
sha16fdf7331d2d0c3f9dca58a1bbf459eda94c29308 \
rmd160 7b4322ab339082077b7630dc4d16aa7853e9cbb0
Error
Copy these 3 checksum lines and change the lines in
/opt/local/var/macports/sources/
rsync.macports.org/release/ports/tex/latexmk/Portfile
so that the checksums that MacPorts matches against are the same as the
checksums of your file.
This is the workaround for all checksum errors. However, I would make sure
that you've downloaded the correct file (run port clean --all latexmk) and
try again before doing the above.
Hope this helps,
Jason
On Mon, Jan 24, 2011 at 10:44 AM, Tim Campbell tim.campb...@nrlssc.navy.mil
wrote:
Is there a work-around for the latexmk checksum error (Ticket #27863)?
-Tim
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Graduate Student
352-392-4032
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Typing in different alphabets in X11 applications? UTF-8 support?
Dear all, I'm trying to type in non-latin alphabets (Spanish, Bulgarian and Hebrew) in X11 applications, however the characters are always shown as latin. In the terminal, the characters are displayed correctly, however, within an X11 application they show up in the Latin alphabet. For example, I can type Добре (in Bulgarian) in the terminal, however, when I type the same in gedit it uses the latin alphabet (Dobre). The same is true for accents in Spanish. I can write Café in the terminal, but in gedit it appears as Caf'e. Does anyone know how to solve this problem? Below some of the things that I have already tried. Best regards, Jochem Attempt 1: set the LC_ALL and LANG variables to en_US.UTF8 in .profile Attempt 2: Set LC_ALL and LANG variables in ~/.MacOSX/environment.plist -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Jochem Liem, MSc. Informatics Institute Faculty of Science University of Amsterdam http://www.science.uva.nl/~jliem/ Phone: +31 (0)20 525 6801 Mobile: +31 (0)6 4321 9992 Fax: +31 (0)20 525 7490 Visitor address: Science Park 904, C2.248 1098 XH Amsterdam Mailing address: Postbus 94323 1090 GH Amsterdam The Netherlands =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Typing in different alphabets in X11 applications? UTF-8 support?
On Jan 24, 2011, at 6:49 PM, Jochem Liem wrote: Dear all, I'm trying to type in non-latin alphabets (Spanish, Bulgarian and Hebrew) in X11 applications, however the characters are always shown as latin. In the terminal, the characters are displayed correctly, however, within an X11 application they show up in the Latin alphabet. For example, I can type Добре (in Bulgarian) in the terminal, however, when I type the same in gedit it uses the latin alphabet (Dobre). The same is true for accents in Spanish. I can write Café in the terminal, but in gedit it appears as Caf'e. Does anyone know how to solve this problem? Below some of the things that I have already tried. I had the same problem with greek alphabet. If you update to the latest version of XQuartz and enable the option Follow system keyboard layout, this should solve your problem. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Typing in different alphabets in X11 applications? UTF-8 support?
Wow, that´s it. Many thanks! Jochem On Mon, Jan 24, 2011 at 5:59 PM, Panayotis Katsaloulis panayo...@panayotis.com wrote: On Jan 24, 2011, at 6:49 PM, Jochem Liem wrote: Dear all, I'm trying to type in non-latin alphabets (Spanish, Bulgarian and Hebrew) in X11 applications, however the characters are always shown as latin. In the terminal, the characters are displayed correctly, however, within an X11 application they show up in the Latin alphabet. For example, I can type Добре (in Bulgarian) in the terminal, however, when I type the same in gedit it uses the latin alphabet (Dobre). The same is true for accents in Spanish. I can write Café in the terminal, but in gedit it appears as Caf'e. Does anyone know how to solve this problem? Below some of the things that I have already tried. I had the same problem with greek alphabet. If you update to the latest version of XQuartz and enable the option Follow system keyboard layout, this should solve your problem. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Jochem Liem, MSc. Informatics Institute Faculty of Science University of Amsterdam http://www.science.uva.nl/~jliem/ Phone: +31 (0)20 525 6801 Mobile: +31 (0)6 4321 9992 Fax: +31 (0)20 525 7490 Visitor address: Science Park 904, C2.248 1098 XH Amsterdam Mailing address: Postbus 94323 1090 GH Amsterdam The Netherlands =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: latexmk checksum error
On Mon, Jan 24, 2011 at 09:44:08AM -0600, Tim Campbell wrote: Is there a work-around for the latexmk checksum error (Ticket #27863)? For this one, the best option is to download the file from the MacPorts distfiles mirror: http://distfiles.macports.org/latexmk/4.21/latexmk.zip and put it in /opt/local/var/macports/distfiles/latexmk/4.21/ The problem here is that the download link is unversioned; it points to the latest version of latexmk, which recently got updated to 4.22. The port is still expecting 4.21. Dan -- Dan R. K. Ports MIT CSAILhttp://drkp.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: latexmk checksum error
On 2011-01-24 16:44 , Tim Campbell wrote: Is there a work-around for the latexmk checksum error (Ticket #27863)? http://trac.macports.org/wiki/FAQ#checksums Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: latexmk checksum error
This worked. Thanks. Is there a way to tell port to use a different mirror? On Jan 24, 2011, at 11:45 AM, Dan Ports wrote: On Mon, Jan 24, 2011 at 09:44:08AM -0600, Tim Campbell wrote: Is there a work-around for the latexmk checksum error (Ticket #27863)? For this one, the best option is to download the file from the MacPorts distfiles mirror: http://distfiles.macports.org/latexmk/4.21/latexmk.zip and put it in /opt/local/var/macports/distfiles/latexmk/4.21/ The problem here is that the download link is unversioned; it points to the latest version of latexmk, which recently got updated to 4.22. The port is still expecting 4.21. Dan -- Dan R. K. Ports MIT CSAILhttp://drkp.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
LaTeXiT build error
Trying to upgrade LaTeXiT from 2.2.0 to 2.3.0. Failure occurs during build of LaTeXiT Helper due to missing PCH files. Below is selection of log that shows one of the errors. Is this a latexit port issue or something else. -Tim :info:build === BUILD NATIVE TARGET LaTeXiT Helper OF PROJECT LaTeXiT WITH CONFIGURATION Development === :info:build Check dependencies :info:build ProcessInfoPlistFile build/Development/LaTeXiT Helper.app/Contents/Info.plist Legacy/LaTeXiT Helper/Info.plist :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline :info:build builtin-infoPlistUtility Legacy/LaTeXiT Helper/Info.plist -genpkginfo /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development/LaTeXiT Helper.app/Contents/PkgInfo -expandbuildsettings -platform macosx -o /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development/LaTeXiT Helper.app/Contents/Info.plist :info:build :info:build CopyStringsFile build/Development/LaTeXiT Helper.app/Contents/Resources/English.lproj/InfoPlist.strings Legacy/LaTeXiT Helper/English.lproj/InfoPlist.strings :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline :info:build setenv ICONV /usr/bin/iconv :info:build /Developer/Library/Xcode/Plug-ins/CoreBuildTasks.xcplugin/Contents/Resources/copystrings --validate --inputencoding utf-8 --outputencoding UTF-16 Legacy/LaTeXiT Helper/English.lproj/InfoPlist.strings --outdir /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development/LaTeXiT Helper.app/Contents/Resources/English.lproj :info:build :info:build CompileXIB Legacy/LaTeXiT Helper/English.lproj/MainMenu.xib :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline :info:build /Developer/usr/bin/ibtool --flatten NO --errors --warnings --notices --output-format human-readable-text --compile /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development/LaTeXiT Helper.app/Contents/Resources/English.lproj/MainMenu.nib /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/Legacy/LaTeXiT Helper/English.lproj/MainMenu.xib --sdk :info:build :info:build CpResource build/Development/LaTeXiT Helper.app/Contents/Resources/latexit.icns Resources/file-icons/latexit.icns :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline :info:build /Developer/Library/PrivateFrameworks/DevToolsCore.framework/Resources/pbxcp -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -resolve-src-symlinks /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/Resources/file-icons/latexit.icns /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development/LaTeXiT Helper.app/Contents/Resources :info:build :info:build CompileC build/LaTeXiT.build/Development/LaTeXiT Helper.build/Objects-normal/x86_64/main.o Legacy/LaTeXiT Helper/main.m normal x86_64 objective-c com.apple.compilers.gcc.4_0 :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline :info:build setenv LANG en_US.US-ASCII :info:build /Developer/usr/bin/gcc-4.0 -x objective-c -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -Wmissing-prototypes -Wreturn-type -Wformat -Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label -Wunused-variable -Wunused-value -Wunknown-pragmas -Wsign-compare -mfix-and-continue -fno-objc-direct-dispatch -mmacosx-version-min=10.6 -gdwarf-2 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/LaTeXiT.build/Development/LaTeXiT Helper.build/LaTeXiT Helper.hmap -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/build/Development -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_LaTeXiT/work/LaTeXiT-mainline/Frameworks -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_r
Re: latexmk checksum error
On Jan 24, 2011, at 11:56, Tim Campbell wrote: This worked. Thanks. Is there a way to tell port to use a different mirror? Not really; it chooses the one it thinks is closest to you. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: LaTeXiT build error
On Jan 24, 2011, at 12:53, Tim Campbell wrote: Trying to upgrade LaTeXiT from 2.2.0 to 2.3.0. Failure occurs during build of LaTeXiT Helper due to missing PCH files. Below is selection of log that shows one of the errors. Is this a latexit port issue or something else. It seems to install OK for me; you may want to file a bug report and attach the complete main.log. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: mingw-binutils: Segmentation fault newer version
On Jan 24, 2011, at 05:43, Mojca Miklavec wrote: I'm experiencing a nasty problem with cross-compiler. I'm using 64-bit Mac OS X 10.6.6 with macports and i386-mingw32-g++ --version i386-mingw32-g++ (GCC) 3.4.5 (mingw-vista special r2) i386-mingw32-ld --version GNU ld (GNU Binutils) 2.19.1 But I would be very very very grateful if somebody from this mailing list could either: - explain me how exactly to compile binutils - or how to create a new port that would fetch binutils 2.21 instead of 2.19.1 and what command to execute to replace the old version with the latest one - or (even better): send me a more recent ld binary for x86_64 Since we're in MacPorts land here, you should probably file a ticket in our issue tracker and request that the maintainer update the i386-mingw32-binutils port to a newer version. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
iOS cross compiling support
hi. I've done the proof-of-concept work on extending macports to handle cross-compiling so that it can be used to maintain 3rd party libs for iOS development. I have successfully built ICU against the iPhone sdk and have it running in the debugger on an iPad. I'd like to turn this work over to a macports developer to be vetted, completed and merged into the mainline build in an appropriate fashion. I didn't know much about the internals of macports and I didn't known anything about TCL. I figured out most of the details as I went along. I'd like to turn the work over to someone more qualified than I am in scripting langauges and macports to complete the project. Is there any interest of the part of the macports developers in accepting the work? NOTE: I did not use your version control system. I modified the scripts in place after the system was installed. I can provide a list of the files I changed and some explanation on what was changed. I basically attempted to piggy-back target/host support on top of the existing variables without changing their function. The approach is fine for proof-of-concept, but the the underlying variables such as os.version and such should be modified and/or renamed to make the design cleaner. However, that task should be done by someone who knows the internals very well and who knows how the changes will affect existing ports. I did have to modify the ICU port file because it has some custom steps that need to be done before its configure script will succeed for a cross-compile. I also had to make an adjustment because of the lack of tzfile.h in the target OS. -James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: iOS cross compiling support
On Jan 24, 2011, at 9:37 PM, James Gregurich wrote: hi. I've done the proof-of-concept work on extending macports to handle cross-compiling so that it can be used to maintain 3rd party libs for iOS development. I have successfully built ICU against the iPhone sdk and have it running in the debugger on an iPad. I'd like to turn this work over to a macports developer to be vetted, completed and merged into the mainline build in an appropriate fashion. I didn't know much about the internals of macports and I didn't known anything about TCL. I figured out most of the details as I went along. I'd like to turn the work over to someone more qualified than I am in scripting langauges and macports to complete the project. Is there any interest of the part of the macports developers in accepting the work? NOTE: I did not use your version control system. I modified the scripts in place after the system was installed. I can provide a list of the files I changed and some explanation on what was changed. I basically attempted to piggy-back target/host support on top of the existing variables without changing their function. The approach is fine for proof-of-concept, but the the underlying variables such as os.version and such should be modified and/or renamed to make the design cleaner. However, that task should be done by someone who knows the internals very well and who knows how the changes will affect existing ports. I did have to modify the ICU port file because it has some custom steps that need to be done before its configure script will succeed for a cross-compile. I also had to make an adjustment because of the lack of tzfile.h in the target OS. Hi James -- Sounds interesting -- could you post your changes as a unified diff? Cheers, Landon ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
