From ooo-dev-return-5917-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Fri Sep 16 08:00:24 2011 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2CCE377EE for ; Fri, 16 Sep 2011 08:00:24 +0000 (UTC) Received: (qmail 74175 invoked by uid 500); 16 Sep 2011 08:00:24 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 74058 invoked by uid 500); 16 Sep 2011 08:00:23 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 74050 invoked by uid 99); 16 Sep 2011 08:00:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2011 08:00:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jogischmidt@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2011 08:00:19 +0000 Received: by bke11 with SMTP id 11so4659351bke.6 for ; Fri, 16 Sep 2011 00:59:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lNo+e/MkDX1V+OeTy2GEiIVpHZGGg+nnPb5Wnh/rVz8=; b=vnuyXAI3u+PgUk9qVaP16BTLZe/tcnAcHd/KKl9mjR7Ex5op4/Kl6Wv83qvMhSDY+m frfJKkp5maQAQ8zOKImBsLHAU76R2sDdHFIsYCwak94q/IWTWXArd5blOQDJAARL8S88 aCc+xDSY9J6Js+V18rs/aCmQqTCB1fxFLtbEw= MIME-Version: 1.0 Received: by 10.204.140.88 with SMTP id h24mr47296bku.170.1316159914572; Fri, 16 Sep 2011 00:58:34 -0700 (PDT) Received: by 10.204.42.16 with HTTP; Fri, 16 Sep 2011 00:58:34 -0700 (PDT) In-Reply-To: References: <35FF95D1-ADF3-47E1-8871-97B44DC7F9EA@Janik.cz> <57B87506-36AE-4DD4-9367-F57818B8FE8F@Janik.cz> <19b8f03940aa990a328338dc54229b06@tutopia.com> Date: Fri, 16 Sep 2011 09:58:34 +0200 Message-ID: Subject: Re: How to do with glibc-2.1.3 in AOOo? From: =?UTF-8?Q?J=C3=BCrgen_Schmidt?= To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0015174c16cc2cfc1e04ad0a5c9b --0015174c16cc2cfc1e04ad0a5c9b Content-Type: text/plain; charset=UTF-8 On Wed, Sep 14, 2011 at 3:42 PM, Tor Lillqvist wrote: > > The question is why do we need this? I would think > > all supported platforms have standard conformant > > C/C++ libs. > > Yeah, but the code uses non-standard library functions, apparently. > See external/glibc/makefile.mk. Apparently what's needed is getopt() > and readdir_r(). > > > In the same line of questioning, but not a license > > issue, why do we need STLport? > > (In LibreOffice we don't use STLport any more on any platform.) Your > code presumably still relies on some STLport stuff on Windows. Anyway, > even if AOOo itself wouldn't use STLport itself, if you want to be > binary compatible with binary extensions, those might rely on the OOo > installation containing a STLport shared library so you need to build > and ship it. > that is correct but i would say it's a minor issue. Extensions where the source is available can be easy recompiled and others have to be recompiled by the vendor if they are still supported. I don't expect too many C++ extensions because of well known reasons. If we detect critical C++ extensions that are not longer supported we can handle them special. Especially for C++ extensions i would always recommend to use a max version dependency. In the long term i would suggest that we remove STL_port as well and use the compiler version. By the way it would be very nice if such work on the code could be shared between the projects that rely more or less on the same base ;-) Independent on the promotion, supporting, etc. on a specific brand we should really think how we can come back to one common source to bundle the developer resources. In the long term we have only success if we work together because our goal is the same. The best free available and stable office productivity suite. Juergen > > --tml > --0015174c16cc2cfc1e04ad0a5c9b--