Opened 9 years ago

Closed 4 years ago

#48183 closed defect (fixed)

libetonyek @0.1.2: build failure on Lion

Reported by: mkae (Marko Käning) Owned by: RJVB (René Bertin)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: libetonyek

Description

This is what the Lion's buildbot ran into:

checking for boost/unordered_map.hpp... yes
checking for glm/glm.hpp... no
configure: error: Required boost headers not found.

Change History (13)

comment:1 Changed 9 years ago by RJVB (René Bertin)

That rings a bell, thought I'd figured that out. Are any of the dependencies less up-to-date on, what is it, 10.7?

comment:2 Changed 9 years ago by RJVB (René Bertin)

IIRC, that error went away for me when I added --with-sysroot=${prefix} to configure.args . Where is glm.hpp installed on 10.7? Looking at the glm portfile it cannot be elsewhere but ${prefix}/include/glm ...

comment:3 Changed 9 years ago by mkae (Marko Käning)

I don't know what to suggest here... We could issue a rebuild on the Lion builder, perhaps.

comment:4 Changed 9 years ago by RJVB (René Bertin)

Don't you have login access to the builders?

comment:5 Changed 9 years ago by mkae (Marko Käning)

Yes, I could issue a rebuild for the Lion builder, if that made sense.

comment:6 Changed 9 years ago by RJVB (René Bertin)

I meant login, try a rebuild, and then twiddle around in order to figure out why you get the error if you keep getting it. You'd need to be able to check the config.log file in the source directory at the least, to see what went wrong with the test checking for glm/glm.hpp .

That's actually something that base should do: attach config.log (if it exists; cmake has similar files) to main.log in case of a failure during the configure phase.

Last edited 9 years ago by RJVB (René Bertin) (previous) (diff)

comment:7 Changed 9 years ago by mkae (Marko Käning)

I don't see how I can access any file directly on a builder, except through the buildbot UI. If browsing stdio of the build phase doesn't give the required information, well then I have no clue what to do. :(

comment:8 in reply to:  6 ; Changed 9 years ago by larryv (Lawrence Velázquez)

Replying to rjvbertin@…:

I meant login, try a rebuild, and then twiddle around in order to figure out why you get the error if you keep getting it.

No, we do not have login access to the Buildbot infrastructure.

comment:9 Changed 9 years ago by RJVB (René Bertin)

That s**ks then ...

Marko, if you still have your 10.6.8 set-up, does the port build there?

comment:10 in reply to:  8 Changed 9 years ago by mkae (Marko Käning)

Replying to larryv@…:

No, we do not have login access to the Buildbot infrastructure.

It would be nice if one could specify files which could be made accessible via the buildbot's UI just like the build log (stdio) itself... Wishful thinking, I know, since someone would have to implement and maintain it.

comment:11 in reply to:  9 Changed 9 years ago by mkae (Marko Käning)

Replying to rjvbertin@…:

That s**ks then ...

Yep.

Marko, if you still have your 10.6.8 set-up, does the port build there?

No, that's gone since a few months and became a Yosemite. :-/

comment:12 Changed 6 years ago by kencu (Ken)

this has been updated to 0.1.9 now, but requires another library (at least) that we don't currently have in MacPorts <https://bitbucket.org/tagoh/liblangtag/wiki/Home> to build.

comment:13 Changed 4 years ago by ken-cunningham-webuse

Resolution: fixed
Status: newclosed

In bd915bd0735d7686fbc0048ac38f8b210eac23c6/macports-ports (master):

libetonyek: blacklist incompatible compilers

fixes build on older systems
closes: #48183

Note: See TracTickets for help on using tickets.