Bug 3205

Summary: Failing chmod when running "make" in buildroot (openssl). /usr/lib should have been /usr/lib64
Product: buildroot Reporter: daniel
Component: OtherAssignee: Gustavo Zacarias <gustavo>
Status: RESOLVED FIXED    
Severity: normal CC: buildroot
Priority: P5    
Version: 2010.11   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Host: Target:
Build:
Attachments: Buildroot "make" output
Buildroot "make" output with engines-symlink workaround
File listing showing the problem
Config file used for buildroot

Description daniel 2011-02-03 11:25:39 UTC
Created attachment 2911 [details]
Buildroot "make" output

> make[1]: Leaving directory `/usr/src/buildroot-2010.11/output/build/openssl-1.0.0b'
> rm -rf /usr/src/buildroot-2010.11/output/target/usr/lib/ssl
> rm -f /usr/src/buildroot-2010.11/output/target/usr/bin/c_rehash
# libraries gets installed read only, so strip fails
> chmod +w /usr/src/buildroot-2010.11/output/target/usr/lib/engines/lib*.so
> chmod: cannot access `/usr/src/buildroot-2010.11/output/target/usr/lib/engines/lib*.so': No such file or directory
> make: *** [/usr/src/buildroot-2010.11/output/build/openssl-1.0.0b/.stamp_target_installed] Error 1


If failes to chmod the files because the engines catalog is in lib64 instead. Added a symlink as a workaround, but then it also tried to chmod libssl.so.* and libcrypto.so.* in the same catalog with the same result. Was able to make it continue by touching those files and setting the permissions, then removing the dummy files afterwards. See attached files for more detailed output
Comment 1 daniel 2011-02-03 11:26:25 UTC
Created attachment 2917 [details]
Buildroot "make" output with engines-symlink workaround
Comment 2 daniel 2011-02-03 11:27:11 UTC
Created attachment 2923 [details]
File listing showing the problem
Comment 3 daniel 2011-02-03 11:28:48 UTC
Created attachment 2929 [details]
Config file used for buildroot
Comment 4 Gustavo Zacarias 2011-02-03 13:00:21 UTC
Can you try the patch at http://repo.or.cz/w/buildroot-gz.git/commitdiff/dddfea987f329a7dea507f987bde59f52b14ddd5 ?
Fixes the issue for me.
Comment 5 daniel 2011-02-03 14:30:05 UTC
Testing it now. Takes a while to build...
Comment 6 Peter Korsgaard 2011-02-23 22:40:23 UTC
Committed fix by Gustavo, thanks