26 Aug
2012
26 Aug
'12
5:15 a.m.
On Friday 24 of August 2012 17:20:08 David C. Rankin wrote:
David,
I read the comments for bug 920, which addresses exactly the same problem.
After all, refers the same proposed patch. But comments confirm what I
have also stated. Patches 18173187 (partially) and 7b10d93d cherry picked
into v3.5.13-sru.
http://bugs.pearsoncomputing.net/show_bug.cgi?id=920#c4
Slavek
--
On 08/24/2012 10:11 AM, David C. Rankin wrote:
> As with the other person who originally posted
> http://trinity-devel.pearsoncomputing.net/?0::6608, the change is
apparently
> necessary so that correct *directory* information
is provided for the
build. You
> must be exporting some path somewhere in your
build such that telling
make to
> use the correct directory information with
'$^' results in double-path
> information in your build. I don't know. It is either broken on your
end
or on
> my end. I'm not using any exports to build,
just the code from GIT.
Building
> just from GIT without altering the environment
requires the patch I
submitted.
I'll test the patch and report back. Looking closely at what my patch
does
and
what your patch does, I appears that they both
accomplish the same thing
regarding the path information from 2 different directions:
AC_PATH_PROGS(MOC_QT3, [moc-tqt], no, [$QT3_PREFIX:$PATH])
You seem to be providing the ':$PATH' information explicitly, while:
'$^' is a list of all the prerequisites of the rule, including the names
of the
directories in which they were found.
What I don't know is which is the 'most correct' way to do it. After
testing,
if your works for my build, I'm happy just pushing
yours. Will report
back.