Re: APBuild

On Tuesday 11 November 2008 09:15:30 Isak Savo wrote:
> On Tue, Nov 11, 2008 at 6:05 PM, Justin Karneges <[email protected]> wrote:
> > FWIW, I'm on a 64-bit machine.  Maybe I don't have any glibc_2.0 stuff?
>
> Aha, that explains a lot. No glibc for 64bit started at 2.3 or 2.4 I
> think. I don't think it's neccessary to use apbuild on 64bit systems
> since there aren't any (known) differences between the versions that
> are deployed today.

Okay, I've built everything now without apbuild.  This feels really weird to 
me because when I think of autopackage I first think of apbuild.  So I guess 
all I'm doing now is building the app raw on my machine.  Here's what I get 
during 'makepackage':

Checking ELF binaries for highest GLIBC versions used ... done with warnings
WARNING: Symbols from glibc 2.3 (or newer) were found. Consider using apbuild 
to allow users of older distros to run this binary.
If you are statically linking any libraries, make sure they are compiled with 
apbuild too.
Scanning and stripping ELF binaries ... done with warnings
WARNING: ELF binary ./bin/barracuda was compiled without apbuild.
WARNING: ./bin/barracuda dynamically links against libXrender.so.1, please 
link statically.

I figure these are just lots of bogus warnings.  But, here's what happens when 
I try to run 'package install':

# Checking for required C library versions ... failed
# FAIL:
# Your copy of glibc, a core system library, is too old for this package.
# You need at least the following symbols in glibc: GLIBC_2.2.5.
#
# This error normally means that whoever built the package did not build it 
correctly.
# Please report the contents of this message to the provider of this package, 
and
# ask them to rebuild it using apbuild.
#
# Upgrading glibc is highly dangerous, so we recommend in this situation that 
you
# compile the app you want to install from the sources if possible. Sorry :(

I suspect I'm testing the release candidate in the nick of time. :)

-Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]