On 14/10/2007, Walter Barnes <[EMAIL PROTECTED]> wrote:
>
> From: michael lang <[EMAIL PROTECTED]>
> >On 14/10/2007, Walter Barnes <[EMAIL PROTECTED]> wrote:
> >>Checking for zlib support... yes (auto-detected)
> >><snip>
> >>cc -lz lspci.o common.o lib/libpci.a -o lspci
> >>lib/libpci.a(names.o): In function `pci_load_name_list':
> >>names.c:(.text+0x4e1): undefined reference to `gzopen'
> >>names.c:(.text+0x57d): undefined reference to `gzgets'
> >>names.c:(.text+0x682): undefined reference to `gzclose'
> >>names.c:(.text+0x6a8): undefined reference to `gzeof'
> >>names.c:(.text+0x737): undefined reference to `gzclose'
> >>names.c:(.text+0xb11): undefined reference to `gzopen'
> >>names.c:(.text+0xc99): undefined reference to `gzerror'
> >>names.c:(.text+0xcb9): undefined reference to `gzclose'
> >
> >Is that detection of zlib from a different package with a configure
> script? PCI Utils doesn't have a >configure in my package...
> >Anyways, what is your current zlib version?
>
> Support for compressing the pciids file was added in version 2.2.4 so the
> version in BLFS doesn't need zlib (it's 2.2.3). The configure script is in
> the lib directory of the source package and is called automatically when you
> run make.
>
> My version of zlib is 1.2.3
>
> Thanks,
> Walter
>

Actually, I use 2.2.6 myself, without knowing there was a configure, though
I just saw that it does indeed get run, oh well.
Anyways, the latest version of zlib is 1.2.3, so you can't upgrade(though
maybe there are improvements using CVS or something, but meh). One
possiblity is that zlib is located in multiple directories(/tools and
/usr/lib?), and maybe a different version is being included. Try to execute
the compile command with a direct link to the link file(/usr/lib/libz.a),
instead of -lz. See if that works, if not, then I'm at a loss(recompile
zlib, watching out for any errors/warnings?).

Michael
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to