1.40.0-beta-20060811
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
http://sarovar.org/download.php/1064/pdftex-1.40.0-beta-20060811.tar.bz2 http://sarovar.org/download.php/1065/pdftex-1.40.0-beta-20060725-20060811.di... --------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060811 was released on 2006-08-11 --------------------------------------------------------------- - renamed primitives: \primitive -> \pdfprimitive \ifprimitive -> \ifpdfprimitive \ifabsdim -> \ifpdfabsdim \ifabsnum -> \ifpdfabsnum - new version of \primitive/\ifprimitive (but see above) - new dimen: \pdfpxdimen - support for jbig2 files - new library: obsdcompat, which has improved string functions and allows the use of __attribute__ - update libpng to 1.2.12 - added JFIF detection patch to writejpg.c (was bug 548) - bugfix: truetype OS/2 v3 fonts (594) - bugfix: file with only \immediate\pdfobj stream results in garbage (505) - bugfix: invalid pdf created if font name contains space (509) Please have a look at libs/obsdcompat; it has a bunch of very nice (and safe) string functions. And it allows the safe use of the __attribute__-feature of gcc. Best Martin
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Martin Schröder wrote:
http://sarovar.org/download.php/1064/pdftex-1.40.0-beta-20060811.tar.bz2 http://sarovar.org/download.php/1065/pdftex-1.40.0-beta-20060725-20060811.di...
--------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060811 was released on 2006-08-11 --------------------------------------------------------------- - renamed primitives: \primitive -> \pdfprimitive \ifprimitive -> \ifpdfprimitive \ifabsdim -> \ifpdfabsdim \ifabsnum -> \ifpdfabsnum
I am still not happy with that renaming. At the moment, I am merging Aleph into luatex. Surely you do not expect me to have \pdfpardir , \pdfocplist etc., so why would there be a pdf prefix for non-pdf related new primitives? (I know we have discussed this before, but ...) Other then that: thanks for the new beta. I will have a look at the obsdcompat library asap. Taco
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Taco Hoekwater wrote:
Martin Schr�der wrote:
http://sarovar.org/download.php/1064/pdftex-1.40.0-beta-20060811.tar.bz2 http://sarovar.org/download.php/1065/pdftex-1.40.0-beta-20060725-20060811..d...
--------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060811 was released on 2006-08-11 --------------------------------------------------------------- - renamed primitives: \primitive -> \pdfprimitive \ifprimitive -> \ifpdfprimitive \ifabsdim -> \ifpdfabsdim \ifabsnum -> \ifpdfabsnum
I am still not happy with that renaming. At the moment, I am merging Aleph into luatex. Surely you do not expect me to have \pdfpardir , \pdfocplist etc., so why would there be a pdf prefix for non-pdf related new primitives? (I know we have discussed this before, but ...)
indeed
Other then that: thanks for the new beta. I will have a look at the obsdcompat library asap.
well, we can use the \pdf prefix in pdftex and no prefix in metatex (luatex); that way those who stick to pdftex < 2 can decide themselves if they want to alias them Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Martin Schröder wrote:
http://sarovar.org/download.php/1064/pdftex-1.40.0-beta-20060811.tar.bz2 http://sarovar.org/download.php/1065/pdftex-1.40.0-beta-20060725-20060811.di...
--------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060811 was released on 2006-08-11 --------------------------------------------------------------- - renamed primitives: \primitive -> \pdfprimitive
But it was still as printed \primitive. The attached patch fixes that Taco
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Hi Martin, Martin Schröder wrote:
Please have a look at libs/obsdcompat; it has a bunch of very nice (and safe) string functions. And it allows the safe use of the __attribute__-feature of gcc.
Since you did some butchering already, would you be willing to
do some more? (i had trouble cross-compiling to windows)
* includes.h
This loads
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
2006/8/16, Taco Hoekwater
Since you did some butchering already, would you be willing to do some more? (i had trouble cross-compiling to windows)
Taco, of course.
* includes.h This loads
and , but I think they are not needed and both give me trouble (pwd.h doesnt exist, and the mingw version of unistd.h does not compile under c++)
time.h seems also to be unneeded.
* strmode.c If you do not intend to use strmode(), please remove the C file (this is not a string function).
Done. A patch is attached.
Otherwise, I have a version that behaves more or less predictable for win32 (group and others settings are identical to user). I can send you that if desired.
I don't have a win32 system to test, so thank you, no. But any source code patches needed for that are welcome. Best Martin
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Martin Schröder wrote:
2006/8/16, Taco Hoekwater
: Since you did some butchering already, would you be willing to do some more? (i had trouble cross-compiling to windows)
Done.
A patch is attached.
Thank you, runs like a charm.
Otherwise, I have a version that behaves more or less predictable for win32 (group and others settings are identical to user). I can send you that if desired.
I don't have a win32 system to test, so thank you, no. But any source code patches needed for that are welcome.
If we don't need it, let it be. I know that the 'write' permission on Windows is not as naive as my quick hack was (user=group=world), but I don't know enough of the Win32 permissions model to fix it properly for inclusion in the official library. Best, Taco
![](https://secure.gravatar.com/avatar/bf0ccc5ca53d1c619bea05b7506db020.jpg?s=120&d=mm&r=g)
On 8/11/06, Martin Schröder
http://sarovar.org/download.php/1064/pdftex-1.40.0-beta-20060811.tar.bz2 http://sarovar.org/download.php/1065/pdftex-1.40.0-beta-20060725-20060811.di...
--------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20060811 was released on 2006-08-11 [...]
Please have a look at libs/obsdcompat; it has a bunch of very nice (and safe) string functions. And it allows the safe use of the __attribute__-feature of gcc.
Until now, pdftex could be built using a c99 compiler. There seems
to be a bug in
gcc 4.1's strsep under "std-c99".
I was able to build this (using the two patches posted to this thread)
on Fedora Core 5 and also SGI Irix 6.5 (using the SGI MIPSPro "c99"
compiler), but both builds had problems in libs/obsdcompat when using
c99.
For FC5, configure failed to detect strsep when using "gcc -std=c99":
$ gcc --version
gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
$ ./my-build
[...]
gcc -std=c99 -g -O2 -march=i686 -Wall -Wpointer-arith -Wuninitialized
-Wsign-compare -Wno-pointer-sign -I. -I.. -I -I/.. -DHAVE_CONFIG_H
-c ../../../src/libs/obsdcompat/strsep.c
../../../src/libs/obsdcompat/strsep.c:53: error: expected identifier
or '(' before '__extension__'
../../../src/libs/obsdcompat/strsep.c:53: error: expected identifier
or '(' before ')' token
make[1]: *** [strsep.o] Error 1
make[1]: Leaving directory
`/nfs/amigo/diomedea/disk2/TeX/src/pdftex-1.40.0-beta-20060811/i686-linux/libs/obsdcompat'
Note the "-I<null>" and "-I<null>/..", which didn't seem to bother
gcc, but did bother SGI's
compiler.
Other people have reported this error with gcc 4.1 and the workaround
is to add -DHAVE_STRSEP to the compiler flags. I got past this by
editing config.h to "#define HAVE_STRSEP 1" and running the last make
step in the build script. The entry in config.log was:
configure:5077: checking whether strsep is declared
configure:5106: gcc -c -std=c99 -g -O2 -march=i686 -Wall
-Wpointer-arith -Wuninitialized -Wsign-compare -Wno-pointer-sign
conftest.c >&5
conftest.c: In function 'main':
conftest.c:50: error: 'strsep' undeclared (first use in this function)
conftest.c:50: error: (Each undeclared identifier is reported only once
conftest.c:50: error: for each function it appears in.)
conftest.c:50: warning: unused variable 'p'
configure:5112: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "OpenBSD-Compat"
[...]
| #define HAVE_STRING_H 1
[...]
| /* end confdefs.h. */
|
| #ifdef HAVE_STRING_H
| # include
![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
2006/8/18, gnwiii@gmail.com
Until now, pdftex could be built using a c99 compiler. There seems to be a bug in gcc 4.1's strsep under "std-c99".
Curious. I can easily build this with gcc 4.1.0 from SuSE 10.1
Other people have reported this error with gcc 4.1 and the workaround is to add -DHAVE_STRSEP to the compiler flags. I got past this by editing config.h to "#define HAVE_STRSEP 1" and running the last make step in the build script. The entry in config.log was:
This defeats the purpose of the configure, which should check for strsep. :-( Best Martin
participants (4)
-
gnwiii@gmail.com
-
Hans Hagen
-
Martin Schröder
-
Taco Hoekwater