Tim, Serghei, All:
I ran into an earlier build error with amarok that indicated a '-fpermissive' problem, so I added the flags Baho had set in other files that let amarok build further until I hit the undefined reference to `Amarok::aboutData' error.
Why the new need for:
CFLAGS=${CFLAGS}" -fpermissive" CXXFLAGS=${CXXFLAGS}" -fpermissive"
in the build?
maybe this help: Downgrade some diagnostics about nonconformant code from errors to warnings. Thus, using -fpermissive will allow some nonconforming code to compile
"man gcc"
On Tue, May 3, 2011 at 10:46 PM, David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
Tim, Serghei, All:
I ran into an earlier build error with amarok that indicated a '-fpermissive' problem, so I added the flags Baho had set in other files that let amarok build further until I hit the undefined reference to `Amarok::aboutData' error.
Why the new need for:
CFLAGS=${CFLAGS}" -fpermissive" CXXFLAGS=${CXXFLAGS}" -fpermissive"
in the build?
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
David C. Rankin -
PICCORO McKAY Lenz