| Summary: | pciutiles can't find libz | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Daniele Salvatore Albano <d.albano> |
| Component: | Other | Assignee: | Thomas Petazzoni <thomas.petazzoni> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | i686 | Target: | i686 |
| Build: | i686 | ||
| Attachments: |
My buildroot config
Patch to fix the issue |
||
|
Description
Daniele Salvatore Albano
2009-08-01 17:28:41 UTC
Created attachment 539 [details]
My buildroot config
(In reply to comment #0) > Hi, > > i was trying to compile pciutiles having zlib but it fails because can't find > lz! > > Probably a path mismatch, but i've done some tests without success. Zlib are > there and works correctly, openssl compiles successfully! > > Here there is the output > make[2]: Leaving directory > `/home/daniele/Development/OPBXA/buildroot-git/build_i686/pciutils-3.0.1/lib' > /home/daniele/Development/OPBXA/buildroot-git/../targets/i686-opbxa-linux-gnu//bin/i686-opbxa-linux-gnu-gcc > -O3 -pipe -O3 --sysroot > /home/daniele/Development/OPBXA/buildroot-git/build_i686/staging_dir/ -Wall -W > -Wno-parentheses -Wstrict-prototypes -Wmissing-prototypes -c -o lspci.o > lspci.c > /home/daniele/Development/OPBXA/buildroot-git/../targets/i686-opbxa-linux-gnu//bin/i686-opbxa-linux-gnu-gcc > -O3 -pipe -O3 --sysroot > /home/daniele/Development/OPBXA/buildroot-git/build_i686/staging_dir/ -Wall -W > -Wno-parentheses -Wstrict-prototypes -Wmissing-prototypes -c -o common.o > common.c > /home/daniele/Development/OPBXA/buildroot-git/../targets/i686-opbxa-linux-gnu//bin/i686-opbxa-linux-gnu-gcc > lspci.o common.o lib/libpci.a -lz -lresolv -o lspci > /home/daniele/Development/OPBXA/targets/i686-opbxa-linux-gnu/bin/../lib/gcc/i686-opbxa-linux-gnu/4.3.3/../../../../i686-opbxa-linux-gnu/bin/ld: > cannot find -lz > broken toolchain and/or toolchain setup. What does $ grep TOOLCHAIN .config say? (In reply to comment #2) > broken toolchain and/or toolchain setup. > What does > $ grep TOOLCHAIN .config > say? > nm, you attached it, sorry. BR2_TOOLCHAIN_EXTERNAL=y Just use the internal toolchain. Why do you say « Just use internal toolchain » ? External toolchains are now supposed to be supported. It's not because you don't personaly care about external toolchain support that other don't. And I do care, for example. Daniele, thanks for the report, I'll have a look at it. Created attachment 541 [details]
Patch to fix the issue
The patch that fixes the issue. I've just sent a pull request for it.
|