#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Comment(by dports@…): Looks like it's trying to do dependency tracking (gcc -M) and can't with multiple arch flags. I feel like we must have dealt with this before, but the only references I can find are to automake programs that support --disable-dependency-tracking, which this does not. -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Comment(by dports@…): I just tried muniversal, actually. It failed with: {{{ Error: Target org.macports.destroot returned: /opt/local/share/doc/groff-1.21/pdf/pdfmark.pdf differs in /opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_sysutils_groff/work/destroot-i386 and /opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_sysutils_groff/work /destroot-x86_64 and cannot be merged }}} I wonder if the pdf files differ only because they are compressed, in which case we should decompress them and rerun the comparison, as we do for .gz files (although I don't know if there's a way to easily decompress a pdf without pulling in esoteric dependencies). Or it's possible they just legitimately differ. (Of course, if there were a solution that didn't require muniversal that would obviously be preferable.) -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Changes (by ryandesign@…): * cc: siavashsf@… (added) Comment: Has duplicate #29066. -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Comment(by ryandesign@…): His patch says: run the configure phase with the settings set in the portfile, then run the configure phase again in a different directory. Ryan, you're right this is not a command listed in the guide or approved for use in portfiles. I am of course also guilty of using this in the php5extension portgroup, and a similar method in the php5 portfile, but I'd rather not proliferate its use if at all possible. Does this second configure script really need all the arguments passed to the main one? Does it for example matter whether --prefix is passed to it? If not, and if the only thing we're concerned with is disabling dependency tracking, then just write a simple one-line patch that unconditionally adds that flag to that configure script invocation; there's no harm in disabling dependency tracking even when not building universal. Dependency tracking is only relevant when a build directory is reused, which in MacPorts it never is; it's cleaned after every successful build. -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Comment(by dtakahashi42@…): Thank you for the better fix. As you pointed, {{{portconfigure::configure_main}}} is not documented (but it is exported to global namespace from {{{${prefix}/share/macports/Tcl/port1.0/portconfigure.tcl}}}), so I should not have used it... In my observation, {{{Makefile}}} at {{{src/libs/gnulib}}} does not install anything, but just build {{{libgnu.a}}} that is statically linked to main binaries. So passing all the configure options is not needed, and I agree to add a small patch that unconditionally disables dependency tracking. -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:16> MacPorts <http://www.macports.org/> Ports system for Mac OS

#29050: groff universal variant fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: universal | Port: groff -------------------------------------+-------------------------------------- Comment(by ryandesign@…): Yes, but we were trying to avoid the muniversal variant if possible. -- Ticket URL: <https://trac.macports.org/ticket/29050#comment:19> MacPorts <http://www.macports.org/> Ports system for Mac OS