Re: Troubles using apbuild

Hi again,

I disabled FORTIFY_SOURCE but I'm still getting those errors:

[...]
./.libs/libmonoruntime.a(threadpool.o): In function `socket_io_epoll_main':
/usr/src/packages/BUILD/mono-2.2/mono/metadata/threadpool.c:598:
undefined reference to `epoll_wait@GLIBC_DONT_USE_THIS_SYMBOL'
[...]

The LSB AppChecker tool tells me that epoll_* symbols were added in GLIBC_2.3.2.
Is there a way to specify that I want apbuild to strip all symbols
except those available in a given glibc version?

Regards,
Mathieu



On Tue, Mar 17, 2009 at 10:55 PM, Isak Savo <[email protected]> wrote:
> On Tue, Mar 17, 2009 at 8:23 PM, Mathieu Cadet <[email protected]> wrote:
>> Hi folks,
>>
>> I'm trying to use apbuild to build more portable binaries.
>>
>> However the documentation for the tool seems to be quite sparse...
>>
>> I'm trying to build mono using apbuild/apgcc and I'm getting the
>> following errors:
>
> Side track, but are you sure you really want to build and ship mono
> yourself? Mono is a system library/runtime and should be handled by
> the distributor or by the upstream project
>
> If you do decide to ship mono with your packages, make sure you
> install it in a private directory so that it doesn't affect other
> programs on the users system.
>
> -Isak
>
> ---------------------------------------------------------------------
> 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]