On 04/30/2018 04:08 PM, Pavel Raiskup wrote:
On Monday, April 30, 2018 2:52:54 PM CEST Florian Weimer wrote:
On 04/09/2018 06:07 PM, Yaakov Selkowitz wrote:
On 2018-04-09 04:40, Florian Weimer wrote:
On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
On 2018-04-09 03:59, Florian Weimer wrote:
On Mon, Apr 30, 2018 at 10:25 AM, Yaakov Selkowitz
wrote:
gedit, like most GNOME components, uses gnome-autogen.sh; in this
particular case, iirc ACLOCAL_PATH="libgd" also needs to be set.
There's also AUTOPOINT='intltoolize --automake --copy' which gedit
needs for
On 2018-04-30 09:01, mcatanz...@gnome.org wrote:
> On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer wrote:
>> Such we change the guidelines to always run autoreconf? This would
>> also help with new architecture bringup because those often need
>> autotools fixes, but it will
On Mon, 2018-04-30 at 09:01 -0500, mcatanz...@gnome.org wrote:
> On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer
> wrote:
> > Such we change the guidelines to always run autoreconf? This
> > would
> > also help with new architecture bringup because those often need
> >
On 04/30/2018 04:01 PM, mcatanz...@gnome.org wrote:
Some packages will not build when autoreconf is called outside
autogen.sh, and these packages typically do not distribute autogen.sh.
E.g. gedit. Packagers would need to work around such issues.
Isn't that against the spirit of the GPLv2 and
On Monday, April 30, 2018 2:52:54 PM CEST Florian Weimer wrote:
> On 04/09/2018 06:07 PM, Yaakov Selkowitz wrote:
> > On 2018-04-09 04:40, Florian Weimer wrote:
> >> On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
> >>> On 2018-04-09 03:59, Florian Weimer wrote:
> Is there a recommend way to
On Mon, Apr 30, 2018 at 7:52 AM, Florian Weimer
wrote:
Such we change the guidelines to always run autoreconf? This would
also help with new architecture bringup because those often need
autotools fixes, but it will choke on really old or manually patched
upstream
On 04/09/2018 06:07 PM, Yaakov Selkowitz wrote:
On 2018-04-09 04:40, Florian Weimer wrote:
On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
On 2018-04-09 03:59, Florian Weimer wrote:
Is there a recommend way to get libtool to pass through all flags
specified in CFLAGS and LDFLAGS unchanged,
On Mon, 2018-04-09 at 11:15 -0500, Yaakov Selkowitz wrote:
> True, if you need to preserve order you need to use -Wl, for each such
> argument, e.g.:
>
> libdemo_la_LDFLAGS = -Xlinker --as-needed -Xlinker -lm -Xlinker
> --no-as-needed -lvirt
>
> or:
>
> libdemo_la_LDFLAGS =
On 2018-04-09 05:21, Daniel P. Berrangé wrote:
> On Mon, Apr 09, 2018 at 04:21:54AM -0500, Yaakov Selkowitz wrote:
>> On 2018-04-09 03:59, Florian Weimer wrote:
>>> Is there a recommend way to get libtool to pass through all flags
>>> specified in CFLAGS and LDFLAGS unchanged, and have the GCC
On 2018-04-09 04:40, Florian Weimer wrote:
> On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
>> On 2018-04-09 03:59, Florian Weimer wrote:
>>> Is there a recommend way to get libtool to pass through all flags
>>> specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
>>> driver sort
On Mon, Apr 09, 2018 at 04:21:54AM -0500, Yaakov Selkowitz wrote:
> On 2018-04-09 03:59, Florian Weimer wrote:
> > Is there a recommend way to get libtool to pass through all flags
> > specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
> > driver sort out which flags to pass to
On 04/09/2018 11:21 AM, Yaakov Selkowitz wrote:
On 2018-04-09 03:59, Florian Weimer wrote:
Is there a recommend way to get libtool to pass through all flags
specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
driver sort out which flags to pass to the compiler/assembler/linker?
On 2018-04-09 03:59, Florian Weimer wrote:
> Is there a recommend way to get libtool to pass through all flags
> specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
> driver sort out which flags to pass to the compiler/assembler/linker?
$ libtool --mode=compile --help
[snip]
This
On 04/09/2018 10:59 AM, Florian Weimer wrote:
Is there a recommend way to get libtool to pass through all flags
specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
driver sort out which flags to pass to the compiler/assembler/linker?
Never mind, I found the old thread again:
Is there a recommend way to get libtool to pass through all flags
specified in CFLAGS and LDFLAGS unchanged, and have the GCC compiler
driver sort out which flags to pass to the compiler/assembler/linker?
Thanks,
Florian
___
devel mailing list --
16 matches
Mail list logo