libgpg-error upgrade fails during build phase on leopard (10.5.8) on PowerBook G4 (PPC 7450)

[zzanderr]

This is probably a duplicate as I accidentally forgot to specify the affected port.

libgpg-error/main.log is attached. I will try deactivating the old libgpg-error, reinstalling and then report the results.

[zzanderr]

libgpg-error main.log

[zzanderr]

No, it still fails with the old libgpg-error deactivated, and then attempting fresh install after port clean --all libgpg-error

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #44920.

[udbraumann]

Cc Me!

[udbraumann]

Also fails on 10.6.8

[Schamschula (Marius Schamschula)]

I have reported this issue upstream:

​https://bugs.g10code.com/gnupg/issue1712

[ctreleaven (Craig Treleaven)]

Cc Me!

[udbraumann]

Replying to mschamschula@…:

I have reported this issue upstream:

​https://bugs.g10code.com/gnupg/issue1712

Any personal guess why 10.5. and 10.6 fail, but 10.7 and 10.8 work?

What I have tried on 10.6.8 is to test all available compilers (apple-gcc, gcc, llvm-gcc, clang) in various versions, but none could handle the lines 825 ff. in gpg-error.h

[Schamschula (Marius Schamschula)]

A quick inspection of main.log seems to indicate that there is an issue with system header files. More specifically "ssize_t" may not have been declared. Adding

 #include <stdlib.h>

to gpg-error.h may solve the issue.

Also see:

​https://developer.apple.com/library/mac/documentation/Darwin/Conceptual/64bitPorting/transition/transition.html

[mndavidoff (Monte Davidoff)]

Cc Me!

[zzanderr]

I just added #include <stdlib.h> to gpg-error.h before configuring, as mschamschula suggested. Still it fails. Could it possibly require both the editing of the header and an alternate compiler?

leopard 10.5.8 PowerBook G4, PPC 7450 XCode 3.14

[raramayo (Rodolfo Aramayo)]

Cc Me!

[Schamschula (Marius Schamschula)]

I just did a bit more digging:

Under OS X 10.9 I find that ssize_t is defined in <sys/types.h>. This may not be the case for the older OS versions. I the back of my mind I remember running into the following patch:

​http://notmuchmail.org/pipermail/notmuch/2009/000272.html

which defines ssize_t.

[zzanderr]

I understand you to be referring to the file
/usr/include/sys/types.h

On my system, this file contains the lines:

{{{ #ifndef _SIZE_T #define _SIZE_T /* DO NOT REMOVE THIS COMMENT: fixincludes needs to see

• _GCC_SIZE_T */

typedef darwin_size_t size_t; #endif

#ifndef _SSIZE_T #define _SSIZE_T typedef darwin_ssize_t ssize_t; #endif }}}

I am running leopard (10.5.8) on a PowerBook G4 (PPC 7450)

[zzanderr]

Oops. Sorry about the formatting, I tried to use the code block feature...

[Schamschula (Marius Schamschula)]

Can you try adding

<sys/types.h>

to gpg-error.h rather than

#include <stdlib.h>

?

[vikingjs@…]

Cc Me!

[zzanderr]

Sorry, adding

#include <sys/types.h>

doesn't work.

[ryandesign (Ryan Carsten Schmidt)]

On my Tiger system, the error I got was basically that off_t was not defined. off_t is defined by the POSIX standard to be defined in sys/types.h. sys/types.h is not included by src/gpg-error.h. Adding #include <sys/types.h> to src/gpg-error.h works for me on Tiger. I'll test on a few other systems before committing.

[ryandesign (Ryan Carsten Schmidt)]

Also fixed the build on Snow Leopard so I committed it in r125206.

[zzanderr]

Oh, so you added

#include <sys/types.h>

to

gpg-error.h.in

I mistakenly added it to

gpg-error.h

I still don't understand all the in's and out's of makefiles, etc...

[zzanderr]

By the way, it compiled. Thanks to both of you!

[ryandesign (Ryan Carsten Schmidt)]

Usually, if there is a file foo.in, then the file foo will be generated from it by the process of running ./configure or possibly by running make.

[zzanderr]

One of these days, hopefully soon, I'm going to read the Gnu Make Manual. Thanks again!

[larryv (Lawrence Velázquez)]

Replying to zanderpower@…:

One of these days, hopefully soon, I'm going to read the Gnu Make Manual.

That won’t tell you about .in files and makefile generation (although you should still read it). You want the Autotools manuals:

• ​http://www.gnu.org/software/autoconf/manual/autoconf.html
  • ​http://www.gnu.org/software/m4/manual/m4.html
• ​http://www.gnu.org/software/automake/manual/automake.html
• ​http://www.gnu.org/software/libtool/manual/libtool.html

[zzanderr]

Great! This will keep me busy for a while :D