Re: MetaPost 1.004 announcement

Re: MetaPost 1.004 announcement

[Thomas A. Schmitz]

On May 1, 2008, at 11:24 AM, Taco Hoekwater wrote:

> The MetaPost team is happy to announce a new release of MetaPost:
>
> ----------------------------------------------------------------------
> MetaPost 1.004
> ----------------------------------------------------------------------
>
> The sources and a win32 package can be downloaded immediately from
>
>   http://foundry.supelec.fr/projects/metapost/
>
> This release will also be available from CTAN soon, and it will be
> included in the next TeXLive. The source package should compile  
> normally
> on all systems that are capable of compiling a modern web2c-based TeX
> distribution.

Hi Taco,

I have two questions/problems with the new release:

1. for my linux box, I just grabbed the linux tarball, but the  
binaries in there still declare they're version 1.003. Is that an  
oversight, or are those indeed old binaries (and you forgot to pack  
the new ones? :-)

2. On OS X 10.5 (intel), compilation aborts with this message:

creating Makefile
creating doc/Makefile
creating lib/Makefile
creating man/Makefile
creating mpware/Makefile
creating mpdir/Makefile
creating web2c/Makefile
creating window/Makefile
cat: ../../../src/texk/web2c/window/Makefile.in: No such file or  
directory
creating fmtutil.cnf
creating c-auto.h
gcc -DHAVE_CONFIG_H  -I. -I../../../../src/texk/web2c/web2c -I../.. - 
I../../../../src/texk/web2c/.. -I.. -I../../../../src/texk/web2c/ 
web2c/..  -g -O2  -c ../../../../src/texk/web2c/web2c/kps.c
In file included from ../../../../src/texk/web2c/../kpathsea/config.h: 
78,
                  from ../../../../src/texk/web2c/web2c/../config.h:44,
                  from ../../../../src/texk/web2c/web2c/web2c.h:3,
                  from ../../../../src/texk/web2c/web2c/kps.c:26:
../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: syntax error  
before '*' token
../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
types for 'calloc'
../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
types for 'malloc'
../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
types for 'realloc'
/usr/include/stdlib.h:176: error: previous declaration of 'realloc'  
was here
../../../../src/texk/web2c/../kpathsea/c-std.h:57: warning: data  
definition has no type or storage class
../../../../src/texk/web2c/web2c/kps.c: In function 'uppercasify':
../../../../src/texk/web2c/web2c/kps.c:36: warning: initialization  
from incompatible pointer type
make: *** [kps.o] Error 1

Any pointers?

Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[luigi scarso]

On Sat, May 3, 2008 at 8:56 PM, Thomas A. Schmitz
<thomas.schmitz@uni-bonn.de> wrote:
>
> On May 1, 2008, at 11:24 AM, Taco Hoekwater wrote:
>
>> The MetaPost team is happy to announce a new release of MetaPost:
>>
>> ----------------------------------------------------------------------
>> MetaPost 1.004
>> ----------------------------------------------------------------------
>>
>> The sources and a win32 package can be downloaded immediately from
>>
>>   http://foundry.supelec.fr/projects/metapost/
>>
>> This release will also be available from CTAN soon, and it will be
>> included in the next TeXLive. The source package should compile
>> normally
>> on all systems that are capable of compiling a modern web2c-based TeX
>> distribution.
>
> Hi Taco,
>
> I have two questions/problems with the new release:
>
> 1. for my linux box, I just grabbed the linux tarball, but the
> binaries in there still declare they're version 1.003. Is that an
> oversight, or are those indeed old binaries (and you forgot to pack
> the new ones? :-)
I have build mpost from src (I always prefer to compile from source)

# mpost
This is MetaPost, Version 1.004 (Web2C 7.5.5)
**
! End of file on the terminal... why?


-- 
luigi
it's new .
it's powerful .
it's luatex .
http://www.luatex.org
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[Peter Münster]

On Sat, May 03 2008, luigi scarso wrote:

> > 1. for my linux box, I just grabbed the linux tarball, but the
> > binaries in there still declare they're version 1.003. Is that an
> > oversight, or are those indeed old binaries (and you forgot to pack
> > the new ones? :-)
> 
> # mpost
> This is MetaPost, Version 1.004 (Web2C 7.5.5)

That means some redundancy in the code: the version number is maintained at
two places ("mpost" and "mpost --version").

Cheers, Peter

-- 
http://pmrb.free.fr/contact/

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[luigi scarso]

On Sun, May 4, 2008 at 7:46 AM, Peter Münster <pmlists@free.fr> wrote:
> On Sat, May 03 2008, luigi scarso wrote:
>
>> > 1. for my linux box, I just grabbed the linux tarball, but the
>> > binaries in there still declare they're version 1.003. Is that an
>> > oversight, or are those indeed old binaries (and you forgot to pack
>> > the new ones? :-)
>>
>> # mpost
>> This is MetaPost, Version 1.004 (Web2C 7.5.5)
>
> That means some redundancy in the code: the version number is maintained at
> two places ("mpost" and "mpost --version").

root@luigicasa-laptop:/opt/luatex/metapost-1.004# grep -r 1.004 src
src/texk/web2c/mp.web:@d banner=='This is MetaPost, Version 1.004'
{printed when \MP\ starts}
src/texk/web2c/mp.web:@d metapost_version=="1.004"



root@luigicasa-laptop:/opt/luatex/metapost-1.004# grep -r 1.003 src
src/texk/web2c/lib/texmfmp.c:#define BANNER "This is MetaPost, Version 1.003"

-- 
luigi
it's new .
it's powerful .
it's luatex .
http://www.luatex.org
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[Taco Hoekwater]

Thomas A. Schmitz wrote:
> 
> I have two questions/problems with the new release:
> 
> 1. for my linux box, I just grabbed the linux tarball, but the 
> binaries in there still declare they're version 1.003. Is that an 
> oversight, or are those indeed old binaries (and you forgot to pack
>  the new ones? :-)

Answered by Peter and Luigi. I 've fixed the repository versions
of texmfmp.c, and will probably update the tarballs tomorrow
(I also have to add that mpboxes.pdf)

> 2. On OS X 10.5 (intel), compilation aborts with this message:

This is the same problem Hans van der Meer ran into with MPlib
a while back. Somehow configure fails to notice that OS X 10.5
has standard C headers just like any other Unix.

If you look at  the configure output, it will say somewhere in
the middle:

   checking for ANSI C header files... no

The build error is a result of that. Hans van der Meer came up
with the following answer (but I have *no* idea how to implement):

> Eureka! I think I found it (took a lot of experimentation).
> 
> Playing with the optimizing options through CFLAGS and setting the
> architecture to the G4 status of my Mac Powerbook, miraculously
> Metafont1.002 did compile under MacOSX10.5. Experimentally I then
> established that the architecture should be specified on the gcc call
> in order to have the proper ANSI headers found; without these
> compilation will get stuck.
> 
> The options that I think relevant are (both CFLAGS and CXXFLAGS
> should be set):
> 
> 1. general architecture specification: CFLAGS -arch ppc      (for
> powerpc) CFLAGS -arch ppc64    (for the new 64bit binaries on
> powerpc) CFLAGS -arch i386     (for intel) I did not check the ppc64
> (not needed) and i386 (not having one) options.
> 
> 2. more specific architecture specification affecting instruction set
> and scheduling if one wants to tune the generated code to ones
> processor: CFLAGS -mcpu=G4 (-mcpu=G5 etc. whichever ones machine has)
> 
> 
> It would be most natural, I think, if the -arch switch is added
> standard through the autoconf scripts. Taco could see to that for
> metapost and luatex, I trust. Can someone mail this experience to the
> maintainers of pdftex? (I could not ascertain why pdftex compiles
> without problems).
> 
> Hans van der Meer

Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[Mojca Miklavec]

On Sun, May 4, 2008 at 10:38 AM, Taco Hoekwater wrote:
> Thomas A. Schmitz wrote:
>  >
>  > 1. general architecture specification: CFLAGS -arch ppc      (for
>  > powerpc) CFLAGS -arch ppc64    (for the new 64bit binaries on
>  > powerpc) CFLAGS -arch i386     (for intel) I did not check the ppc64
>  > (not needed) and i386 (not having one) options.
>  >
>  > 2. more specific architecture specification affecting instruction set
>  > and scheduling if one wants to tune the generated code to ones
>  > processor: CFLAGS -mcpu=G4 (-mcpu=G5 etc. whichever ones machine has)
>  >
>  >
>  > It would be most natural, I think, if the -arch switch is added
>  > standard through the autoconf scripts. Taco could see to that for
>  > metapost and luatex, I trust. Can someone mail this experience to the
>  > maintainers of pdftex? (I could not ascertain why pdftex compiles
>  > without problems).

I might be missing the point, but I would be glad if -arch would not
be set automatically if there is some better solution. Now it's really
easy to cross-compile metapost, pdfTeX and LuaTeX for ppc on intel. If
configure script would set the -arch unconditionally, then I would
probably run into problems. But again - I might be misunderstanding
the problem.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: MetaPost 1.004 announcement

[Thomas A. Schmitz]

On May 4, 2008, at 10:38 AM, Taco Hoekwater wrote:

> Thomas A. Schmitz wrote:
>>
>> I have two questions/problems with the new release:
>>
>> 1. for my linux box, I just grabbed the linux tarball, but the
>> binaries in there still declare they're version 1.003. Is that an
>> oversight, or are those indeed old binaries (and you forgot to pack
>> the new ones? :-)
>
> Answered by Peter and Luigi. I 've fixed the repository versions
> of texmfmp.c, and will probably update the tarballs tomorrow
> (I also have to add that mpboxes.pdf)

Thanks, Taco.

>
>
>> 2. On OS X 10.5 (intel), compilation aborts with this message:
>
> This is the same problem Hans van der Meer ran into with MPlib
> a while back. Somehow configure fails to notice that OS X 10.5
> has standard C headers just like any other Unix.
>
> If you look at  the configure output, it will say somewhere in
> the middle:
>
>   checking for ANSI C header files... no
>
> The build error is a result of that. Hans van der Meer came up
> with the following answer (but I have *no* idea how to implement):
>
>> Eureka! I think I found it (took a lot of experimentation).
>>
>> Playing with the optimizing options through CFLAGS and setting the
>> architecture to the G4 status of my Mac Powerbook, miraculously
>> Metafont1.002 did compile under MacOSX10.5. Experimentally I then
>> established that the architecture should be specified on the gcc call
>> in order to have the proper ANSI headers found; without these
>> compilation will get stuck.
>>
>> The options that I think relevant are (both CFLAGS and CXXFLAGS
>> should be set):
>>
>> 1. general architecture specification: CFLAGS -arch ppc      (for
>> powerpc) CFLAGS -arch ppc64    (for the new 64bit binaries on
>> powerpc) CFLAGS -arch i386     (for intel) I did not check the ppc64
>> (not needed) and i386 (not having one) options.
>>
>> 2. more specific architecture specification affecting instruction set
>> and scheduling if one wants to tune the generated code to ones
>> processor: CFLAGS -mcpu=G4 (-mcpu=G5 etc. whichever ones machine has)
>>
>>
>> It would be most natural, I think, if the -arch switch is added
>> standard through the autoconf scripts. Taco could see to that for
>> metapost and luatex, I trust. Can someone mail this experience to the
>> maintainers of pdftex? (I could not ascertain why pdftex compiles
>> without problems).
>>
>> Hans van der Meer
>
> Best wishes,
> Taco

Thanks again. I simply issued export CFLAGS="-arch i386" and could  
compile without problems.

Thanks, and best wishes

Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Metapost on OS X 10.5

[Taco Hoekwater]

[-- Attachment #1: Type: text/plain, Size: 2843 bytes --]


Hi Thomas,

Can you please replace the c-std.h in src/texk/kpathsea
with the attached one and see if that helps? The one I
am distributing with metapost is slightly different from the
one in tl, and we need to exclude differences that from the list
of causes (either that, or we found the cause)

Best wishes,
Taco

Thomas A. Schmitz wrote:
> 
> Hi Taco,
> 
> I have two questions/problems with the new release:
> 
> 1. for my linux box, I just grabbed the linux tarball, but the  
> binaries in there still declare they're version 1.003. Is that an  
> oversight, or are those indeed old binaries (and you forgot to pack  
> the new ones? :-)
> 
> 2. On OS X 10.5 (intel), compilation aborts with this message:
> 
> creating Makefile
> creating doc/Makefile
> creating lib/Makefile
> creating man/Makefile
> creating mpware/Makefile
> creating mpdir/Makefile
> creating web2c/Makefile
> creating window/Makefile
> cat: ../../../src/texk/web2c/window/Makefile.in: No such file or  
> directory
> creating fmtutil.cnf
> creating c-auto.h
> gcc -DHAVE_CONFIG_H  -I. -I../../../../src/texk/web2c/web2c -I../.. - 
> I../../../../src/texk/web2c/.. -I.. -I../../../../src/texk/web2c/ 
> web2c/..  -g -O2  -c ../../../../src/texk/web2c/web2c/kps.c
> In file included from ../../../../src/texk/web2c/../kpathsea/config.h: 
> 78,
>                   from ../../../../src/texk/web2c/web2c/../config.h:44,
>                   from ../../../../src/texk/web2c/web2c/web2c.h:3,
>                   from ../../../../src/texk/web2c/web2c/kps.c:26:
> ../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: syntax error  
> before '*' token
> ../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
> types for 'calloc'
> ../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
> types for 'malloc'
> ../../../../src/texk/web2c/../kpathsea/c-std.h:57: error: conflicting  
> types for 'realloc'
> /usr/include/stdlib.h:176: error: previous declaration of 'realloc'  
> was here
> ../../../../src/texk/web2c/../kpathsea/c-std.h:57: warning: data  
> definition has no type or storage class
> ../../../../src/texk/web2c/web2c/kps.c: In function 'uppercasify':
> ../../../../src/texk/web2c/web2c/kps.c:36: warning: initialization  
> from incompatible pointer type
> make: *** [kps.o] Error 1
> 
> Any pointers?
> 
> Thomas
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #2: c-std.h --]
[-- Type: text/plain, Size: 2961 bytes --]

/* c-std.h: the first header files.

   Copyright 1992, 1993, 1994, 1995, 1996, 1997, 2008 Karl Berry.
   Copyright 1999, 2005 Olaf Weber.

   This library is free software; you can redistribute it and/or
   modify it under the terms of the GNU Lesser General Public
   License as published by the Free Software Foundation; either
   version 2.1 of the License, or (at your option) any later version.

   This library is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
   Lesser General Public License for more details.

   You should have received a copy of the GNU Lesser General Public License
   along with this library; if not, see <http://www.gnu.org/licenses/>.  */

#ifndef KPATHSEA_C_STD_H
#define KPATHSEA_C_STD_H

/* Header files that essentially all of our sources need, and
   that all implementations have.  We include these first, to help with
   NULL being defined multiple times.  */
/* Workaround against a <math.h> MSVC bug : it can't be declared 
   extern "C" in a c++ source file. */
#ifndef __cplusplus
#include <math.h>
#endif
#include <stdio.h>

/* Be sure we have constants from <unistd.h>.  */
#include <kpathsea/c-unistd.h>

#ifdef HAVE_STDLIB_H
#include <stdlib.h>
/* Include <stdlib.h> before <stddef.h>, to help avoid NULL
   redefinitions on some systems.  (We don't include <stddef.h>
   ourselves any more, but FYI.)  */
#else
/* It's impossible to say for sure what the system will deign to put in
   <stdlib.h>, but let's hope it's at least this.  */
extern char *getenv ();
#endif /* not HAVE_STDLIB_H */

#ifdef WIN32
#include <malloc.h>
#else
#ifndef STDC_HEADERS
#ifndef ALLOC_RETURN_TYPE
#define ALLOC_RETURN_TYPE void
#endif /* not ALLOC_RETURN_TYPE */
extern ALLOC_RETURN_TYPE *calloc (), *malloc (), *realloc ();
#endif /* not STDC_HEADERS */
#endif /* not WIN32 */

/* SunOS 4.1.1 gets STDC_HEADERS defined, but it doesn't provide
   EXIT_FAILURE.  So far no system has defined one of EXIT_FAILURE and
   EXIT_SUCCESS without the other.  */
#ifndef EXIT_SUCCESS
#ifdef VMS
#define EXIT_SUCCESS 1
#define EXIT_FAILURE 0
#else
#define EXIT_SUCCESS 0
#define EXIT_FAILURE 1
#endif
#endif /* not EXIT_SUCCESS */

/* strchr vs. index, memcpy vs. bcopy, etc.  */
#include <kpathsea/c-memstr.h>

/* Error numbers and errno declaration.  */
#include <kpathsea/c-errno.h>

/* Numeric minima and maxima.  */
#include <kpathsea/c-minmax.h>

/* Assertions are too useful to not make generally available.  */
#ifdef HAVE_ASSERT_H
#include <assert.h>
#else
#define assert(expr) /* as nothing */
#endif

#ifdef VMS
#include <unixlib.h>
#include <unixio.h>
#else
#ifndef WIN32
/* `popen' and `pclose' are part of POSIX.2, not POSIX.1.  So
   STDC_HEADERS isn't enough.  */
extern FILE *popen ();
extern int pclose ();
#endif /* not WIN32 */
#endif /* not VMS */

#endif /* not KPATHSEA_C_STD_H */

[-- Attachment #3: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Metapost on OS X 10.5

[Thomas A. Schmitz]

Hi Taco,

thanks, will try that, but I'm away from my OS X box till late this  
afternoon. I will keep you posted!

Best

Thomas

On May 6, 2008, at 8:50 AM, Taco Hoekwater wrote:

> Hi Thomas,
>
> Can you please replace the c-std.h in src/texk/kpathsea
> with the attached one and see if that helps? The one I
> am distributing with metapost is slightly different from the
> one in tl, and we need to exclude differences that from the list
> of causes (either that, or we found the cause)
>
> Best wishes,
> Taco

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: Metapost on OS X 10.5

[Thomas A. Schmitz]

Hi Taco, Hi Karl,

looks like you nailed it: with the new c-std.h, compilation works  
without a hitch on my 10.5 box!

Best wishes

Thomas

On May 6, 2008, at 8:50 AM, Taco Hoekwater wrote:

> Hi Thomas,
>
> Can you please replace the c-std.h in src/texk/kpathsea
> with the attached one and see if that helps? The one I
> am distributing with metapost is slightly different from the
> one in tl, and we need to exclude differences that from the list
> of causes (either that, or we found the cause)
>
> Best wishes,
> Taco

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________