You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hudson (Commented) (JIRA)" <ji...@apache.org> on 2012/03/19 12:01:38 UTC

[jira] [Commented] (ZOOKEEPER-1384) test-cppunit overrides LD_LIBRARY_PATH and fails if gcc is in non-standard location

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232555#comment-13232555 ] 

Hudson commented on ZOOKEEPER-1384:
-----------------------------------

Integrated in ZooKeeper-trunk #1500 (See [https://builds.apache.org/job/ZooKeeper-trunk/1500/])
    ZOOKEEPER-1384. test-cppunit overrides LD_LIBRARY_PATH and fails if gcc is in non-standard location (Jay Shrauner via phunt) (Revision 1302281)

     Result = SUCCESS
phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1302281
Files : 
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml

                
> test-cppunit overrides LD_LIBRARY_PATH and fails if gcc is in non-standard location
> -----------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1384
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1384
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: build, tests
>    Affects Versions: 3.4.2
>         Environment: Linux
>            Reporter: Jay Shrauner
>            Assignee: Jay Shrauner
>            Priority: Minor
>             Fix For: 3.4.4, 3.5.0
>
>         Attachments: ZOOKEEPER-1384.patch
>
>
> On Linux with gcc installed in /usr/local and the libs in /usr/local/lib64, test-core-cppunit fails because zktest-st is unable to find the right libstdc++.
> build.xml is overriding the environment LD_LIBRARY_PATH instead of appending to it. This should be changed to match the treatment of PATH by appending the desired extra path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira