Re: unable to upgrade/build texlive-bin

2013-04-02 Thread MAS!
 clang can in some cases use a lot more RAM than gcc did. Try updating to 
 Xcode 4.6.1 if you haven't already. Also ensure your command line tools are 
 up to date by open Xcode,

I'm updating che command line tools..
but I'm compiling it (even with the outdated command line tools) without the 
+motif option

may be there are troubles with it?
what change with or without the +motif?!
thank you for all
bye 
MAS!

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: unable to upgrade/build texlive-bin

2013-04-02 Thread Dan Ports
On Mon, Apr 01, 2013 at 12:25:14PM +0200, MAS! wrote:
 I'm under mountain lion and I wish to upgrade texlive-bin (2012_5  2012_6) 
 but it seems it goes in loop and eat all memory and even all 'swap', until 
 the disk is full :-(

I'm seeing this now too (it's apparently specific to some combination
of clang/OS version, as I didn't before, and neither did the buildbot)

It looks like clang is choking badly on a character encoding problem in
makejvf.

I've opened http://trac.macports.org/ticket/38643 for this issue, and
just disabled building makejvf for now as a workaround (r104809).

Dan

-- 
Dan R. K. PortsUW CSEhttp://drkp.net/
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


unable to upgrade/build texlive-bin

2013-04-01 Thread MAS!
Hi
I'm under mountain lion and I wish to upgrade texlive-bin (2012_5  2012_6) but 
it seems it goes in loop and eat all memory and even all 'swap', until the disk 
is full :-(

anyone had the same problem?
or it need more than 4G ram and 12G swap to build it?

thank you in advance

(...)

/usr/bin/clang -DHAVE_CONFIG_H -I. 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/texlive-bin/work/texlive-20120708.26940-source-stripped/texk/ptexenc
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/texlive-bin/work/texlive-20120708.26940-source-stripped/texk/ptexenc
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/texlive-bin/work/texlive-20120708.26940-source-stripped/texk
 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/texlive-bin/work/texlive-20120708.26940-source-stripped/texk
  -isystem/opt/local/include -Wimplicit -Wreturn-type 
-Wdeclaration-after-statement -Wno-unknown-pragmas -pipe -O2 -arch x86_64 -MT 
main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c
main.c:199:25: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
  fputs2(-C   ĹC2Υ⡼A5C9\n, stderr);
^~~~
main.c:200:23: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
  fputs2(-K TFMfile 
C8F3B4C1BBFAC9F4CDѤU+02FAEEC0AEA4B9A4EBPSA5եA9A5F3A5C8TFM̾\n,
 stderr);
   ^~~~
main.c:201:14: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
  fputs2(-b BFF4C3CD
A5١BCA5B9A5饤A5F3CAE4C0B5\n, stderr);
  ^~~~
main.c:202:25: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
  fputs2( 
ʸBBFAA4ι⤵A4F21000A4ȤB7A4C6C0B0BFF4A4ǻD8C4EA\n,
 stderr);
^~~~
main.c:203:23: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]
  fputs2( 
A5ץ饹A4C7ʸBBFAA4ACB2BCA4ACA4U+A862A5ޥA4A5ʥB9A4C7ʸBBFAA4ACBE夬A4EB\n,
 stderr);
   ^~~~
main.c:204:23: warning: illegal character encoding in string literal 
[-Winvalid-source-encoding]

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: unable to upgrade/build texlive-bin

2013-04-01 Thread Ryan Schmidt

On Apr 1, 2013, at 05:25, MAS! urk...@libero.it wrote:

 I'm under mountain lion and I wish to upgrade texlive-bin (2012_5  2012_6) 
 but it seems it goes in loop and eat all memory and even all 'swap', until 
 the disk is full :-(
 
 anyone had the same problem?
 or it need more than 4G ram and 12G swap to build it?

clang can in some cases use a lot more RAM than gcc did. Try updating to Xcode 
4.6.1 if you haven't already. Also ensure your command line tools are up to 
date by open Xcode, visiting its Preferences window, and going to its Downloads 
section.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users