On Tue, Jun 25, 2024 at 06:46:04PM +0200, Bruno Haible wrote:
> > Building shared libraries which depend upon
> > other libraries breaks whenever a dependency found (by something like
> > AC_SEARCH_LIBS) was not built with -fPIC (or whatever
> > the name of this option might be on the platform in q
Building shared libraries which depend upon
other libraries breaks whenever a dependency found (by something like
AC_SEARCH_LIBS) was not built with -fPIC (or whatever
the name of this option might be on the platform in question).
And, preferably, one might want to check that the dependency is
a dy
On Sat, Apr 27, 2024 at 11:42:23PM +0200, Bruno Haible wrote:
> dmitrii.pasechnik wrote:
> > By the way, ac_cv_sys_largefile_opts isn't fun to use - as sometimes
> > it's a plain text, and sometimes flags which should be added to CFLAGS.
> > So one has to write things like
> >
> > AS_CASE([$ac_cv_
On Sat, Apr 27, 2024 at 02:26:24PM -0700, Paul Eggert wrote:
> On 2024-04-27 14:06, dmitrii.pasech...@cs.ox.ac.uk wrote:
> > Thus I got questions whether a patch for a build system I submitted for
> > a project is OK, as it uses an undocumented variable (thus, perhaps,
> > unstable).
>
> Although
Hello,
I am not 100% sure whether this should go to a gnulib list or to an autoconf
list,
but anyway, ac_cv_sys_largefile_opts (from a subroutine in
AC_SYS_LARGEFILE) is not documented in either gnulib manual, or in
autoconf manual. (It is documented in the source).
Thus I got questions whether a
On Fri, Mar 29, 2024 at 12:54:12PM +0100, Darshit Shah wrote:
> I think you make some fair points on the contributions made by people with a
> passable knowledge of the language.
> However, when I said "maintained", I kind of assumed that there will be
> someone with a good enough command over t
On Mon, Feb 06, 2023 at 04:22:46PM -0500, Jeffrey Walton wrote:
> On Sun, Feb 5, 2023 at 9:45 PM Paul Eggert wrote:
> >
> > On 2023-02-05 18:00, Bruno Haible wrote:
> > > Why call it 'c-nullptr', not 'nullptr'?
> >
> > I was worried about C++, not that I know much about it, and operated by
> > ana
On Thu, Aug 25, 2022 at 11:02:59PM -0500, Paul Eggert wrote:
> On 8/25/22 18:20, dmitrii.pasech...@cs.ox.ac.uk wrote:
> >
> > There has been no official gnulib release in like 8 years...
>
> As far as I'm concerned none of the releases have been "official".
> Gnulib simply doesn't work that way.
On Thu, Aug 25, 2022 at 11:02:59PM -0500, Paul Eggert wrote:
> On 8/25/22 18:20, dmitrii.pasech...@cs.ox.ac.uk wrote:
> >
> > There has been no official gnulib release in like 8 years...
>
> As far as I'm concerned none of the releases have been "official".
> Gnulib simply doesn't work that way.
Hi Paul,
On Thu, Aug 25, 2022 at 02:35:26PM -0500, Paul Eggert wrote:
> On 8/25/22 09:53, dmitrii.pasech...@cs.ox.ac.uk wrote:
> > I don't think this is how gnulib is usually used, and that's why regular
> > releases are badly needed.
>
> It's how Gnulib developers (who do maintain other packages)
On Thu, Feb 08, 2018 at 11:43:08AM +0100, Bruno Haible wrote:
> Wesley Viana wrote:
> > So I was wondering how to contribute by "packing" gnulib into a brew
> > formula.
>
> Packaging gnulib through a packaging system (such as Debian, pkg, BSD ports,
> or brew) is, in the current state of things,
11 matches
Mail list logo
