That looks unrelated to this
particular jira, but may be similar to another jira I reported recently on hue 
rpm build is being broken (can't find it from phone, but should be easy to 
find). I had to temporarily comment out hue in bigtop.mk to make full clean 
build pass.

-Sent from mobile, please excuse typos
Mikhail

> On Jan 11, 2014, at 16:19, Bruno Mahé (JIRA) <[email protected]> wrote:
> 
> 
>    [ 
> https://issues.apache.org/jira/browse/BIGTOP-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868907#comment-13868907
>  ] 
> 
> Bruno Mahé commented on BIGTOP-1168:
> ------------------------------------
> 
> I am getting a build error on fedora 18:
> 
> {noformat}
> + cp 
> /run/media/bruno/HDFS/freesoftware/bigtop-asf/build/hue//rpm//SOURCES/hue.init
>  
> /run/media/bruno/HDFS/freesoftware/bigtop-asf/build/hue/rpm/BUILDROOT/hue-2.5.2-1.fc18.x86_64//etc/rc.d/init.d/hue
> + '[' '%{buildarch}' = noarch ']'
> + QA_CHECK_RPATHS=1
> + case "${QA_CHECK_RPATHS:-}" in
> + /usr/lib/rpm/check-rpaths
> *******************************************************************************
> *
> * WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
> *          to fail. To ignore these errors, you can set the '$QA_RPATHS'
> *          environment variable which is a bitmask allowing the values
> *          below. The current value of QA_RPATHS is 0x0000.
> *
> *    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
> *               issue but are introducing redundant searchpaths without
> *               providing a benefit. They can also cause errors in multilib
> *               environments.
> *    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
> *               nor relative filenames and can therefore be a SECURITY risk
> *    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
> *               SECURITY risk
> *    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
> *               RPATHs; this is just a minor issue but usually unwanted
> *    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
> *               and they cause unneeded work while loading libraries
> *    0x0020 ... an RPATH references '..' of an absolute path; this will break
> *               the functionality when the path before '..' is a symlink
> *          
> *
> * Examples:
> * - to ignore standard and empty RPATHs, execute 'rpmbuild' like
> *   $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
> * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
> *   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
> *  
> *******************************************************************************
> ERROR   0002: file 
> '/usr/lib/hue/build/env/lib/python2.7/site-packages/python_ldap-2.3.13-py2.7-linux-x86_64.egg/_ldap.so'
>  contains an invalid rpath '/usr/local/openldap-2.3/lib' in 
> [/usr/local/openldap-2.3/lib]
> error: Bad exit status from /var/tmp/rpm-tmp.K0sQj5 (%install)
> 
> 
> RPM build errors:
>    Bad exit status from /var/tmp/rpm-tmp.K0sQj5 (%install)
> make: *** [/run/media/bruno/HDFS/freesoftware/bigtop-asf/build/hue//.rpm] 
> Error 1
> {noformat}
> 
>> hue build fails (unresolvable maven dependencies)
>> -------------------------------------------------
>> 
>>                Key: BIGTOP-1168
>>                URL: https://issues.apache.org/jira/browse/BIGTOP-1168
>>            Project: Bigtop
>>         Issue Type: Bug
>>   Affects Versions: 0.7.0
>>           Reporter: Mikhail Antonov
>>           Assignee: Mikhail Antonov
>>             Labels: build, hue
>>            Fix For: 0.8.0
>> 
>>        Attachments: BIGTOP-1168.1.patch, BIGTOP-1168.2.patch
>> 
>> 
>> (i may be doing somethin' wrong) building current master and facing this 
>> problem:
>> http://grokbase.com/t/cloudera/hue-user/13bnfjzm9g/compilation-error-due-to-unresolved-pom-dependency-for-hue-3-0-0-and-hue-2-5-1-in-mac
>> Git-cloned hue 2.5.1 from cloudera repo - doesn't  build either. Error:
>> The project com.cloudera.hue:hue-parent:2.5.1-SNAPSHOT 
>> (/projects/cloudera/hue/maven/pom.xml) has 1 error
>> [ERROR]     Non-resolvable parent POM: Failure to find 
>> com.cloudera:parent:pom:1.0-SNAPSHOT in 
>> https://repository.cloudera.com/content/repositories/snapshots was cached in 
>> the local repository, resolution will not be reattempted until the update 
>> interval of cloudera.snapshots.repo has elapsed or updates are forced and 
>> 'parent.relativePath' points at wrong local POM @ line 22, column 11 -> 
>> [Help 2]
>> The recommended fix by the hue guy was to remove parent section from the 
>> pom. So in case others observe the same, i'm attaching small patch with 
>> oneliner sed to make build pass.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.1.5#6160)

Reply via email to