Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#27009 closed defect (fixed)

liblastfm : configure : no variable qtdir

Reported by: develop@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: qtdir Cc: ak.ml@…
Port: liblastfm

Description

Hi guys,

:info:configure Good, your configure is finished! Now type: make
:debug:configure Executing proc-post-org.macports.configure-configure-0
:error:configure Target org.macports.configure returned: can't read "qtdir": no such variable
:debug:configure Backtrace: can't read "qtdir": no such variable
    while executing
"$post $targetname"

I saw in the devel list (http://lists.macosforge.org/pipermail/macports-dev/2010-October/013052.html) that André Kaplan modified the portfile recently to clean qtdir variable declaration. But in the post-configure part there is still a call to the variable qtdir. :

post-configure {
    # create Makefile's, then patch them to remove a flaw made by qmake.
    # (1) find subdir Makefile names from top-level Makefile, and have
    # 'make' create each in turn.
    foreach tMf [exec grep -e "Makefile\[\^ \]\*:" ${worksrcpath}/Makefile | \
                     sed -e "s@\\(\[^ \]*/Makefile\[^ \]*\\):\[^ \]*@\\1@g"] {
        system "cd ${worksrcpath} && PATH=${qtdir}/bin:$env(PATH) make ${tMf}"
    }

    # (2) find all created Makefile*'s, and reinplace the offending flaw
    foreach tMf [exec find ${worksrcpath} -name "Makefile*"] {
        reinplace "s@\\(-arch \[^ \]*\\) -arch@\\1@" ${tMf}
    }
}

So this step fails.

Sorry to not helping resolve the problem, I'm not skilled enough. Please Andre what can we do?

Thanks

Change History (2)

comment:1 Changed 14 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

Fix in r72773. Thanks for catching this typo. Please do:

sudo port clean liblastfm
sudo port selfupdate
sudo port install liblastfm

and verify that it works for you. I'm closing this ticket, but please do reopen it this change does not resolve the problem for you.

comment:2 Changed 14 years ago by develop@…

Resolved. Thanks

Note: See TracTickets for help on using tickets.