Re: New buildlist program for APBuild (experimental)

I work developing applications for old machines using old distros
(Slackware 10.2 for instance). Before using apbuild, I had to use a
separate gcc and libc version to cross compile my applications in my
own machine. I happen to use autopackage to install my software too,
but I benefit much from apbuild alone.

I tested the apbuild you sent and had this error:

/usr/include/apbuild/buildlist: error while loading shared libraries:
libgee.so.0: cannot open shared object file: No such file or directory

After installing the package containing this lib I ran apgcc again and
got a nice message:

Generating /home/serra/.config/apbuild/apsymbols.h

But, after some time:

/usr/bin/ld: .obj/release/libdbpool.so: No symbol version section for
versioned symbol
`pthread_cond_signal@GLIBC_DONT_USE_THIS_VERSION_2.3.2'
/usr/bin/ld: final link failed: Nonrepresentable section on output

apsymbols is full of GLIBC_DONT_USE_THIS_VERSION* stuff...

2009/6/13 Jan Niklas Hasse <[email protected]>:
> Hi everyone,
>
> I've written a new buildlist program for APBuild. Furthermore I've
> added that the apsymbols.h file is created just before compilation.
> This allows you to change the minimum required glibc version on the
> fly using the new APBUILD_MINIMUM_GLIBC environment variable.
>
> Changelog: http://trac.autopackage.org/changeset/2566
> New buildlist.vala:
> http://trac.autopackage.org/browser/apbuild/trunk/buildlist.vala
>
> The new program is written in Vala. IMHO a very nice programming
> language which I want to use more often in Autopackage. The advantage
> is that it has no other dependency than glib and that it's far more
> easier than Bash or C. It's translated to C so we can use apgcc for
> compilation. Have a look: http://live.gnome.org/Vala
> You can get autopackages here: http://watteimdocht.de/autopackage/vala
>
> The new APBuild surely needs more testing. Please help me with that,
> you can get a beta build here:
> http://watteimdocht.de/autopackage/Autopackage%20Development%20Environment%201.4.2.package
>
> I would like to seperate APBuild more from Autopackage. For example it
> should have an own autopackage. I had some discussion (Can you "have a
> discussion" in English?) with people on IRC who are using APBuild but
> not Autopackage. I also think that the Zeroinstall, Klik or Listaller
> developers could use a tool like apbuild, too, couldn't they?
>
> So long,
> Jan Niklas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
> For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
>
>

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