tmux: does not build on 10.4

[200309@…]

Tried to:

port install tmux

And it failed.

10.4.11
PowerBook G3 Pismo 500MHz

Does it require a newer system? or?

see attached main.log

Bill

[cooljeanius (Eric Gallager)]

This seems like the key part of the log:

:info:build osdep-darwin.c:23:21: error: libproc.h: No such file or directory
:info:build osdep-darwin.c: In function ‘osdep_get_cwd’:
:info:build osdep-darwin.c:57: error: storage size of ‘pathinfo’ isn’t known
:info:build osdep-darwin.c:64: warning: implicit declaration of function ‘proc_pidinfo’
:info:build osdep-darwin.c:65: error: ‘PROC_PIDVNODEPATHINFO’ undeclared (first use in this function)
:info:build osdep-darwin.c:65: error: (Each undeclared identifier is reported only once
:info:build osdep-darwin.c:65: error: for each function it appears in.)
:info:build make: *** [osdep-darwin.o] Error 1

[cooljeanius (Eric Gallager)]

My libproc.h is in /usr/include and the comment block at the top says

 * Copyright (c) 2006, 2007, 2010 Apple Inc. All rights reserved.

Leopard wasn't released until 2007, so I don't see why Tiger wouldn't have it, too...

[cooljeanius (Eric Gallager)]

libproc.h as it exists on Lion

[cooljeanius (Eric Gallager)]

Actually looking at it again, all the function prototypes have __OSX_AVAILABLE_STARTING and then either __MAC_10_5, __MAC_10_6, or __MAC_10_7 in them... You might be out of luck here...

[200309@…]

Is there a way to determine if a port will compile on PowerPC 10.4?

That is, what are system requirements for a particular port?

[cooljeanius (Eric Gallager)]

Replying to 200309@…:

Is there a way to determine if a port will compile on PowerPC 10.4?

That is, what are system requirements for a particular port?

It's normally up to the portfile author to put something like the following code block in their portfile:

pre-fetch {
    if {${os.platform} == "darwin" && ${os.major} < 9} {
        ui_error "${name} is only supported on OS X 10.5 Leopard or later."
        return -code error "unsupported platform version"
    }
}

Although I'd like it if this were handled by base though... Edit: made a new ticket for that idea: #38508

[200309@…]

Replying to egall@…:

Actually looking at it again, all the function prototypes have __OSX_AVAILABLE_STARTING and then either __MAC_10_5, __MAC_10_6, or __MAC_10_7 in them... You might be out of luck here...

ok tried to compile 10.5 PPC and it works

--->  Cleaning tmux
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

[200309@…]

Replying to egall@…:

Replying to 200309@…:

Is there a way to determine if a port will compile on PowerPC 10.4?

That is, what are system requirements for a particular port?

It's normally up to the portfile author to put something like the following code block in their portfile:

pre-fetch {
    if {${os.platform} == "darwin" && ${os.major} < 9} {
        ui_error "${name} is only supported on OS X 10.5 Leopard or later."
        return -code error "unsupported platform version"
    }
}

Although I'd like it if this were handled by base though... Edit: made a new ticket for that idea: #38508

Oh yes! That would be great.

Rather than waiting for a compile to finish, I would know right away whether I am using a supported platform.

[larryv (Lawrence Velázquez)]

Replying to 200309@…:

Although I'd like it if this were handled by base though... Edit: made a new ticket for that idea: #38508

Oh yes! That would be great.

Rather than waiting for a compile to finish, I would know right away whether I am using a supported platform.

That would not have helped because tmux upstream doesn’t list supported platforms; a MacPorts user would have had to run into problems for us to even know. I guess you won that particular lottery.

[jmroot (Joshua Root)]

libproc.h is part of dtrace, which was added in 10.5. Apparently tmux uses proc_pidinfo to find out some stuff. Who knows how it would have done it in the olden days before dtrace...

[cooljeanius (Eric Gallager)]

After tmux was updated to 1.8 in r104642, it looks like Snow Leopard started seeing a similar issue to this one: #38588

[yeled@…]

Hi I've committed r105099

Can you test, please?

[200309@…]

Replying to yeled@…:

Hi I've committed r105099

Can you test, please?

ok... failed.

see attached main.log

[anddam (Andrea D'Amore)]

Cc Me!

[cooljeanius (Eric Gallager)]

Cc Me!

[mf2k (Frank Schima)]

Assigning to current maintainer.

[tessus (Helmut K. C. Tessarek)]

I took over the maintenance of tmux when 1.9a came out.

As for this particular issue: I don't have a 10.4 system to do any tests or development. My oldest system is 10.6.8. Please tell me what you expect me to do?

[200309@…]

I do not expect you to do anything.

When I tried compiling tmux on 10.4, it did not work, so reported the issue.

I still use 10.4 as I support clients with legacy hardware. But... tmux is no longer important to me.

Thank you for the response.

[tessus (Helmut K. C. Tessarek)]

I'm not saying that I don't want to fix it, I just don't have the means.

If someone gave me access to a 10.4 box, I could have a look. I can't promise anything, since I don't know, if it's even possible, but at least I could try.

If you don't need tmux anymore, please close the ticket. It seems that I'm missing a few permissions on this Trac system, which means I can't close the ticket.

[200309@…]

What kind of access would you need? ssh?

I can set up a Mac with 10.4, dev tools, macports, and give you ssh access. Would you want to do that?

If you are near Santa Cruz, California, I could loan you the Mac.

[tessus (Helmut K. C. Tessarek)]

Yep, ssh is perfect. For the moment I only need the OS and the dev tools (gcc or clang, automake, autoconf, and the typical libs like glibc).

If I am able to compile tmux plus its dependencies manually, we can proceed to the installation of MacPorts, although when I think about it, the installation of MacPorts doesn't really take that long anyway. First I need to figure out, if tmux (libevent2 and ncurses) do even compile on 10.4. It might be possible that there are certain requirements which I can't fix by patching tmux.

[tessus (Helmut K. C. Tessarek)]

With help of the OP I was able to create a fix for this problem. See Ticket #44552. This ticket can be closed.

[neverpanic (Clemens Lang)]

Fix from #44552 committed in r123176.