Re: Compile/Link 101

2013-10-06 Thread Jeremy Huddleston Sequoia
On Oct 5, 2013, at 16:59, Ryan Schmidt wrote: > > On Oct 5, 2013, at 18:13, Craig Treleaven wrote: > >> At 4:06 PM -0500 10/5/13, Ryan Schmidt wrote: >> My somewhat hazy recollection is that it might have started working in >> 4.4. Unfortunately I don't have that version handy to check

Re: Compile/Link 101

2013-10-05 Thread Ryan Schmidt
On Oct 5, 2013, at 18:13, Craig Treleaven wrote: > At 4:06 PM -0500 10/5/13, Ryan Schmidt wrote: >> >>> My somewhat hazy recollection is that it might have started working in > 4.4. Unfortunately I don't have that version handy to check. >> >> http://trac.macports.org/ticket/36339#comment:3

Re: Compile/Link 101

2013-10-05 Thread Craig Treleaven
At 4:06 PM -0500 10/5/13, Ryan Schmidt wrote: >>> My somewhat hazy recollection is that it might have started working in 4.4. Unfortunately I don't have that version handy to check. http://trac.macports.org/ticket/36339#comment:3 says 4.4.1's clang doesn't support LIBRARY_PATH either. 4.5's

Re: Compile/Link 101

2013-10-05 Thread Ryan Schmidt
>>> My somewhat hazy recollection is that it might have started working in >>> 4.4. Unfortunately I don't have that version handy to check. http://trac.macports.org/ticket/36339#comment:3 says 4.4.1's clang doesn't support LIBRARY_PATH either. 4.5's does. So since the build system is so finicky

Re: Compile/Link 101

2013-10-05 Thread Craig Treleaven
Sorry, I'd had a few different tabs open and must have pasted the link from the wrong one. I've bent Michael's ear on this before, but Myth's build system is extremely hard for me to follow particularly due to QMake. Different platforms get different qmkspec files--which are actually a chai

Re: Compile/Link 101

2013-10-05 Thread Michael Dickens
I think Craig is referring to the comment within the Portfile for qt4-mac, about 2/5 of the way down under "Block various compilers". MacPorts' build of Qt4 requires the use of CPATH and LIBRARY_PATH, and post-configure I remove any -I${prefix}/lib entries to keep them from appearing at inappropria

Re: Compile/Link 101

2013-10-05 Thread Joshua Root
On 2013-10-6 00:53 , Craig Treleaven wrote: > At 11:03 PM -0400 10/4/13, Lawrence Velázquez wrote: >> MacPorts sets the LIBRARY_PATH environment variable in the configure >> phase, which sufficiently recent compilers take into account when >> linking. I don't know exactly when Clang started respect

Re: Compile/Link 101

2013-10-05 Thread Joshua Root
On 2013-10-6 00:53 , Craig Treleaven wrote: > BTW, I realize I could set a -L flag in LDFLAGS but Myth includes > modified versions of FFMPEG, dvdnav and a few other libraries. The > contents of LDFLAGS gets included early in the link line and therefore > will try to link against any MacPorts-inst

Re: Compile/Link 101

2013-10-05 Thread Craig Treleaven
At 11:03 PM -0400 10/4/13, Lawrence Velázquez wrote: On Oct 4, 2013, at 9:39 PM, Craig Treleaven wrote: I actually don't know how the test _can succeed_ with XCode 5? There is no '-L' flag to indicate that the library is under /opt/local/lib. MacPorts sets the LIBRARY_PATH environment v

Re: Compile/Link 101

2013-10-04 Thread Lawrence Velázquez
On Oct 4, 2013, at 9:39 PM, Craig Treleaven wrote: > I actually don't know how the test _can succeed_ with XCode 5? There is no > '-L' flag to indicate that the library is under /opt/local/lib. MacPorts sets the LIBRARY_PATH environment variable in the configure phase, which sufficiently rece

Compile/Link 101

2013-10-04 Thread Craig Treleaven
Could someone please explain some very basic stuff about compiling/linking C and C++ code? For a new version of Myth, the configure script succeeds with XCode 5 on Mtn Lion and _fails_ with XCode 4.3 on Lion. The bit that I'm looking at just tests whether certain libraries (faac in this cas