Opened 10 years ago

Closed 10 years ago

#20145 closed defect (fixed)

libXaw-1.0.6 Changeset 53301 can cause build failure

Reported by: sidney@… Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc:
Port: xorg-libXaw


These new lines in changeset 53301 to the libXaw Portfile

# Delete this, so it searches its own headers first rather than installed ones
configure.cppflags-delete -I/opt/local/include

break the build if it causes configure.cppflags to be deleted completely. I get an error

can't read "configure.cppflags"

If I add the following line after the delete, it builds ok, but I don't know enough to say if that is the correct fix:

configure.cppflags-append -I/opt/local/include

Change History (4)

comment:1 Changed 10 years ago by sidney@…

I should have pasted in the complete error message in context, just to make sure it is clear:

--->  Configuring xorg-libXaw
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (xorg-libXaw)
Error: Target org.macports.configure returned: can't read "configure.cppflags": no such variable

comment:2 Changed 10 years ago by sidney@…

I entered the port wrong in the bug summary. It should be xorg-libXaw not libXaw

comment:3 Changed 10 years ago by blb@…

Owner: changed from macports-tickets@… to jeremyhu@…
Port: xorg-libXaw added; libXaw removed

This sounds like #17865 (which was fixed on trunk but apparently wasn't pushed into the 1.7 release); the workaround for tcl (in r44859) may work here as well.

comment:4 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.