| Summary: | make install problem with unstripped binaries | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Lionel Landwerlin <llandwerlin> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: |
no strip fix
related buildroot config |
||
Created attachment 727 [details]
no strip fix
Created attachment 729 [details]
related buildroot config
Well... my fix just does not work. but replacing TARGET_STRIP=true -Not_stripping by TARGET_STRIP=true Not_stripping seems to fix the problem. (In reply to comment #0) > Hi, > > when BR2_STRIP_none=y, I get this error : It would normally make sense to enable BR2_ENABLE_DEBUG (build packages with debugging symbols) if you want unstripped binaries. If that is done, then libglib2 will use the make install-exec target instead, which doesn't call strip. But ok, if shouldn't break anyway, so I'll fix the 'true' argument in git - Thanks. |
Hi, when BR2_STRIP_none=y, I get this error : >>> libglib2 2.20.5 Installing to target /usr/bin/make -j1 DESTDIR=/home/users/llandwer/local/src/buildroot/output/target install-strip -C /home/users/llandwer/local/src/buildroot/output/build/libglib2-2.20.5/ make[1]: Entering directory `/local/src/buildroot/output/build/libglib2-2.20.5' /usr/bin/make INSTALL_PROGRAM="/bin/sh /home/users/llandwer/local/src/buildroot/output/build/libglib2-2.20.5/install-sh -c -s" \ install_sh_PROGRAM="/bin/sh /home/users/llandwer/local/src/buildroot/output/build/libglib2-2.20.5/install-sh -c -s" INSTALL_STRIP_FLAG=-s \ `test -z 'true -Not_stripping' || \ echo "INSTALL_PROGRAM_ENV=STRIPPROG=true -Not_stripping"` install /usr/bin/make: invalid option -- N Usage: make [options] [target] ... Options: -b, -m Ignored for compatibility. -B, --always-make Unconditionally make all targets. -C DIRECTORY, --directory=DIRECTORY I'm currently trying to fix it with the attached patch.