headers
Monic Polynomial | 1 Jun 2009 15:49
Picon
Favicon
Gravatar

New Fink-related blog

There's a new blog on the block:

http://finkers.wordpress.com/

Feel free to contribute. Packagers might want to announce packages- 
that-could-use-some-testing, ask for feedback, write tips on Fink, its  
packages, or porting software to Mac OS X. Drop me an e-mail if you  
want to be added as an author.

Cheers,

--
monipol

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
Permalink | Reply | 0 comments |
headers
Martin Costabel | 2 Jun 2009 03:03
Picon

Bug in qt4-mac-4.5

qt4-mac-4.5 breaks building of texmacs. I tracked this down to the file 
<QtGui/qmacdefines_mac.h> in /sw/lib/qt4-mac/include/, which did not 
exist in qt4-mac-4.4.

That file does some preprocessor macro tricks with the DEBUG symbol (see 
below) that a) don't look useful and b) look wrong, like if the author 
did not understand how preprocessor macros work, which is weird, 
considering that the whole file consist basically of #defines.

Here is what happens: If you #define DEBUG as whatever value you want, 
then #include <QtGui/qmacdefines_mac.h> or indirectly via 
<Qt/qwindowdefs.h>, then you will find that the symbol DEBUG's value has 
changed into a literal "OLD_DEBUG". This breaks any program that uses 
DEBUG as a preprocessor macro and the qt4-mac GUI.

My question is first, whether anyone has seen this bug mentioned (I 
didn't find it on google), and second, how to best fix or work around it.

The macros in question come in 2 blocks, with some other code in 
between. They only make sense if the code in between wants DEBUG=0, but 
I have not seen why this should be the case, hence a) above. The macros are:

#undef OLD_DEBUG
#ifdef DEBUG
# define OLD_DEBUG DEBUG
# undef DEBUG
#endif
#define DEBUG 0
...
#undef DEBUG
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jean-François Mertens | 2 Jun 2009 15:17
Picon
Favicon

Re: Bug in qt4-mac-4.5


On 02 Jun 2009, at 03:03, Martin Costabel wrote:

> ...
> The idea is clear, but preprocessor macros don't work like that.

Really thanks for making so clear msgs !
FInally I understand for sure that cpp works
like tex's \def rather than \edef _ and I'll
feel much more comfortable using it knowing
for sure the right interpretation !
(and I guess there are no analogues of \edef or \let ?)

Thanks !

JF

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
Permalink | Reply | 3 comments |
headers
Martin Costabel | 2 Jun 2009 17:12
Picon

Re: Bug in qt4-mac-4.5

Jean-François Mertens wrote:
> 
> On 02 Jun 2009, at 03:03, Martin Costabel wrote:
> 
>> ...
>> The idea is clear, but preprocessor macros don't work like that.
> 
> Really thanks for making so clear msgs !
> FInally I understand for sure that cpp works
> like tex's \def rather than \edef _ and I'll
> feel much more comfortable using it knowing
> for sure the right interpretation !
> (and I guess there are no analogues of \edef or \let ?)

The most difficult thing was to find out how to print the value of a 
macro at a given moment. From a diving expedition into the depths of the 
docs, I brought home some macros that give the following small example 
program in C:

#include <stdio.h>
// stringify the value of a macro for printing
#define str(x) #x
#define xstr(x) str(x)
// play with replacing macros
#define OLD_DEBUG 1
#define DEBUG OLD_DEBUG
int main(){
         printf("Before: %s\n", xstr(DEBUG));
#undef OLD_DEBUG
         printf("After : %s\n", xstr(DEBUG));
(Continue reading)

Permalink | Reply | 2 comments |
headers
Monic Polynomial | 2 Jun 2009 17:40
Picon
Favicon
Gravatar

Re: Bug in qt4-mac-4.5

On 02/06/2009, at 12:12, Martin Costabel wrote:
> The most difficult thing was to find out how to print the value of a
> macro at a given moment. From a diving expedition into the depths of  
> the
> docs, I brought home some macros that give the following small example
> program in C:
>
> #include <stdio.h>
> // stringify the value of a macro for printing
> #define str(x) #x
> #define xstr(x) str(x)
> // play with replacing macros
> #define OLD_DEBUG 1
> #define DEBUG OLD_DEBUG
> int main(){
>         printf("Before: %s\n", xstr(DEBUG));
> #undef OLD_DEBUG
>         printf("After : %s\n", xstr(DEBUG));
>         return(0);
> }
>
> If you compile and run this, it prints
>
> costabel% ./a.out
> Before: 1
> After : OLD_DEBUG
>
> I don't know enough to say that there are no analogues of \edef or  
> \let,
> but I haven't come across them yet.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin Costabel | 2 Jun 2009 19:59
Picon

Re: Bug in qt4-mac-4.5

Monic Polynomial wrote:
> On 02/06/2009, at 12:12, Martin Costabel wrote:
>> The most difficult thing was to find out how to print the value of a
>> macro at a given moment. From a diving expedition into the depths of  
>> the
>> docs, I brought home some macros that give the following small example
>> program in C:
>>
>> #include <stdio.h>
>> // stringify the value of a macro for printing
>> #define str(x) #x
>> #define xstr(x) str(x)
>> // play with replacing macros
>> #define OLD_DEBUG 1
>> #define DEBUG OLD_DEBUG
>> int main(){
>>         printf("Before: %s\n", xstr(DEBUG));
>> #undef OLD_DEBUG
>>         printf("After : %s\n", xstr(DEBUG));
>>         return(0);
>> }
>>
>> If you compile and run this, it prints
>>
>> costabel% ./a.out
>> Before: 1
>> After : OLD_DEBUG
>>
>> I don't know enough to say that there are no analogues of \edef or  
>> \let,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Macks | 2 Jun 2009 21:14

Help test GNOME2.26 packages

My CVS exp/ has most of the core packages of gnome2.26, "build and
work for me on 10.4/ppc" but would appreciate some build-testing on
intel machines before this is unleashed into unstable. The
language-bindings (c++, perl, python) and anything depending on them
are not done yet, but may as well get the major libs out.

http://fink.cvs.sourceforge.net/viewvc/fink/experimental/dmacks/finkinfo/gnome-2.26/

dan

--

-- 
Daniel Macks
dmacks <at> netspace.org
http://www.netspace.org/~dmacks

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
Permalink | Reply | 1 comment |
headers
David Reiser | 3 Jun 2009 04:55
Picon
Favicon

tetex-base won't install

Prompted by someone on the gnucash list, I tried rebuilding tetex-base  
3.0-1006. The build completed, but post-install fails with:

updmap: Map file links:
psfonts.map -> psfonts_t1.map
pdftex.map -> pdftex_dl14.map
dvipdfm.map -> dvipdfm_dl14.map

/sw/bin/dpkg: error processing tetex-base (--install):
  subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
  tetex-base
### execution of /sw/bin/dpkg-lockwait failed, exit code 1
Failed: can't install package tetex-base-3.0-1006

Earlier in the scrollback, the only thing I see that looks like an  
error is:

fmtutil: running `pdfetex -ini   -jobname=mptopdf -progname=context - 
translate-file=cp227.tcx mptopdf.tex' ...
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX)
  (/sw/share/texmf-dist/web2c/cp227.tcx)
(/sw/share/texmf-dist/tex/generic/context/mptopdf.tex
(/sw/share/texmf-dist/tex/context/base/syst-tex.tex
(/sw/share/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers, parameters, fonts,
skipping \font in plain
skipping \font in plain
skipping \font in plain
skipping \font in plain
(Continue reading)

Permalink | Reply | 15 comments |
headers
David R. Morrison | 3 Jun 2009 05:20
Favicon

Re: tetex-base won't install

Yes, I also had an email directly from a user about this.  It  
mystifies me.

Your message has more information, so I'll try to investigate a bit.

   -- Dave

On Jun 2, 2009, at 7:55 PM, David Reiser wrote:

> Prompted by someone on the gnucash list, I tried rebuilding tetex-base
> 3.0-1006. The build completed, but post-install fails with:
>
> updmap: Map file links:
> psfonts.map -> psfonts_t1.map
> pdftex.map -> pdftex_dl14.map
> dvipdfm.map -> dvipdfm_dl14.map
>
> /sw/bin/dpkg: error processing tetex-base (--install):
>   subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
>   tetex-base
> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1
> Failed: can't install package tetex-base-3.0-1006
>
> Earlier in the scrollback, the only thing I see that looks like an
> error is:
>
> fmtutil: running `pdfetex -ini   -jobname=mptopdf -progname=context -
> translate-file=cp227.tcx mptopdf.tex' ...
> This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX)
(Continue reading)

Permalink | Reply | 14 comments |
headers
Martin Costabel | 3 Jun 2009 09:44
Picon

Re: tetex-base won't install

David R. Morrison wrote:
> Yes, I also had an email directly from a user about this.  It  
> mystifies me.

It happens to me, too, when I simply run `fink reinstall tetex-base`. My 
first guess is that the final error refers to the message shown below, 
which functionally is just a warning, but technically is treated as an 
error message. Looking at the date, and trying to make sense of the 
mathematics with which latex.ltx computes "five years", I guess it is 
possible that this error shows up only after June 1st, 2009.

My personal suggestion is to take a hint from this and switch from tetex 
to texlive. I have been using the texlive packages by Tomoaki Okayama 
for the last couple of weeks daily without any problem.

Here is the message that shows up in those format builds that fail 
(there are quite a few that succeed, basically anything that does not 
involve latex.ltx):

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! You are attempting to make a LaTeX format from a source file
! That is more than five years old.
!
! If you enter <return> to scroll past this message then the format
! will be built, but please consider obtaining newer source files
! before continuing to build LaTeX.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! LaTeX source files more than 5 years old!.
l.540 ...aTeX source files more than 5 years old!}
(Continue reading)

Permalink | Reply | 13 comments |

Gmane