Re: APBuild

On Wed, Nov 12, 2008 at 8:50 PM, Jan Niklas Hasse <[email protected]> wrote:
> On Wed, Nov 12, 2008 at 8:36 PM, Justin Karneges <[email protected]> wrote:
>> I get those missing GLIBC_2.0 symbols, as mentioned earlier in the thread.
>> Isak replied saying I should not use apgcc to compile 64-bit programs.
>
> Ah, i see.

Right now there's not much need. The purpose of apbuild is to support
older systems, and since 64bit distros are a relatively new thing,
apbuild doesn't really do much good.

That said. History has taught us that compatibility gets broken once
in a while so in the future apbuild may be needed for 64bit systems
aswell.

> I'm not sure, but the GLIBC symbols isn't everything apbuild does, so
> there is a reason to run apgcc on 64 bit, is there actually?

True. The bogus dependency stripper could surely benefit 64bit
binaries too. Aswell as the other niceties added by apbuild.

I tend to (wrongly) think of apbuild as the tool-to-fix-glibc-errors :)

> If yes, we should think then how apgcc is triggering this particular
> linker error and then disable the feature for x86_64.

Agree.

-Isak

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