[MacPorts] #48183: libetonyek @0.1.2: build failure on Lion
#48183: libetonyek @0.1.2: build failure on Lion --------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libetonyek --------------------+------------------------- [http://build.macports.org/builders/buildports-lion-x86_64/builds/29501 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. }}} -- Ticket URL: <https://trac.macports.org/ticket/48183> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by rjvbertin@…): 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? -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by rjvbertin@…): 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` ... -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by mk@…): I don't know what to suggest here... We could issue a rebuild on the Lion builder, perhaps. -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by rjvbertin@…): Don't you have login access to the builders? -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by mk@…): Yes, I could issue a rebuild for the Lion builder, if that made sense. -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by 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. 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) in case of a failure during the configure phase. -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by mk@…): I don't see how I can access any file directly on a builder, except through the [https://build.macports.org/builders/buildports-lion-x86_64 buildbot UI]. If browsing {{{stdio}}} of the build phase doesn't give the required information, well then I have no clue what to do. :( -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by larryv@…): Replying to [comment:6 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. -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by rjvbertin@…): That s`**`ks then ... Marko, if you still have your 10.6.8 set-up, does the port build there? -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by mk@…): Replying to [comment:8 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. -- Ticket URL: <https://trac.macports.org/ticket/48183#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
#48183: libetonyek @0.1.2: build failure on Lion -------------------------+------------------------- Reporter: mk@… | Owner: rjvbertin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libetonyek | -------------------------+------------------------- Comment (by mk@…): Replying to [comment:9 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. :-/
-- Ticket URL: <https://trac.macports.org/ticket/48183#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts