On 10 Jan 2014, at 10:24, Markus Hitter wrote:
> Am 10.01.2014 09:26, schrieb Richard Frith-Macdonald:
>> However, I tried your patch as follows:
>>
>> $ cd Documentation
>> $ make
>
> Unbelievable!
That I should test your patch using the most common sequence of commands rather
than the par
On 10 Jan 2014, at 09:43, Richard Frith-Macdonald
wrote:
>
> On 10 Jan 2014, at 08:26, Richard Frith-Macdonald
> wrote:
>
>>
>> On 9 Jan 2014, at 19:49, Markus Hitter wrote:
>>
>>> Am 08.01.2014 13:11, schrieb Niels Grewe:
In fact it’s very, very easy to switch the documentation to
Am 10.01.2014 09:26, schrieb Richard Frith-Macdonald:
> However, I tried your patch as follows:
>
> $ cd Documentation
> $ make
Unbelievable!
What from ...
Am 09.01.2014 20:49, schrieb Markus Hitter:
> The only minor problem not solved is, "make -C Documentation distclean"
> _without_ configur
On 10 Jan 2014, at 08:26, Richard Frith-Macdonald
wrote:
>
> On 9 Jan 2014, at 19:49, Markus Hitter wrote:
>
>> Am 08.01.2014 13:11, schrieb Niels Grewe:
>>> In fact it’s very, very easy to switch the documentation to using the
>>> present (not yet installed) configuration: You just have to
On 9 Jan 2014, at 19:49, Markus Hitter wrote:
> Am 08.01.2014 13:11, schrieb Niels Grewe:
>> In fact it’s very, very easy to switch the documentation to using the
>> present (not yet installed) configuration: You just have to set
>> GNUSTEP_MAKEFILES=../ at the beginning of Documentation/GNUmake
Am 08.01.2014 13:11, schrieb Niels Grewe:
> In fact it’s very, very easy to switch the documentation to using the
> present (not yet installed) configuration: You just have to set
> GNUSTEP_MAKEFILES=../ at the beginning of Documentation/GNUmakefile.
After evaluating this more closely, it's indeed
On 8 Jan 2014, at 14:57, Sebastian Reitenbach
wrote:
>
> On Wednesday, January 8, 2014 14:54 CET, Richard Frith-Macdonald
> wrote:
>
>>
>> On 8 Jan 2014, at 12:38, Markus Hitter wrote:
>>
>>> Am 08.01.2014 13:11, schrieb Niels Grewe:
Markus expects it to use the configuration you j
Hi,
Sebastian Reitenbach wrote:
I think this is mostly a problem packagers are facing.
For example, I create a package for gnustep-make, then install it.
But then, I'm done with it. at least on OpenBSD, there is no
easy way, to rely on an installed version of the same package,
to build additiona
On 8 Jan 2014, at 14:53, Markus Hitter wrote:
> Am 08.01.2014 14:54, schrieb Richard Frith-Macdonald:
>> On 8 Jan 2014, at 12:38, Markus Hitter wrote:
>>
>>> Thank you. That's entirely the point. Because in some environments
>>> there is no "last installed version of gnustep-make".
>>
>> I'd
On Wednesday, January 8, 2014 14:54 CET, Richard Frith-Macdonald
wrote:
>
> On 8 Jan 2014, at 12:38, Markus Hitter wrote:
>
> > Am 08.01.2014 13:11, schrieb Niels Grewe:
> >> Markus expects it to use the configuration you just set using make’s
> >> configure script, while it in fact will
Am 08.01.2014 14:54, schrieb Richard Frith-Macdonald:
> On 8 Jan 2014, at 12:38, Markus Hitter wrote:
>
>> Thank you. That's entirely the point. Because in some environments
>> there is no "last installed version of gnustep-make".
>
> I'd still like to know why you can't set one up?
Simply set
On 8 Jan 2014, at 12:38, Markus Hitter wrote:
> Am 08.01.2014 13:11, schrieb Niels Grewe:
>> Markus expects it to use the configuration you just set using make’s
>> configure script, while it in fact will use the configuration of the
>> last installed version of gnustep-make.
I eventually got t
Am 08.01.2014 13:11, schrieb Niels Grewe:
> Markus expects it to use the configuration you just set using make’s
> configure script, while it in fact will use the configuration of the
> last installed version of gnustep-make.
Thank you. That's entirely the point. Because in some environments there
Hi guys,
I think I finally get what Markus’ problem is. The question is rather not
whether installing gnustep-make should implicitly install its documentation,
the question rather is which configuration you expect the ./Documentation
subdirectory to use. Markus expects it to use the configurati
On 7 Jan 2014, at 21:31, Markus Hitter wrote:
> This prerequisite you talk about is a
> showstopper in some environments and does not solve the problem. If
> having showstoppers is the intention, I feel sorry for GNUstep.
Please, please, calm down and try to help me here;
I'm asking for infor
For those on the -dev mailing list, we're talking about this bug:
https://savannah.gnu.org/bugs/?41125#comment0
Am 07.01.2014 15:17, schrieb Richard Frith-Macdonald:
> I might guess that the issue you mean [...]
Instead of guessing I'd prefer you'd try with the shell snippets I
provided. They
Am 07.01.2014 21:32, schrieb Richard Frith-Macdonald:
> To me the term 'shell snippet' means a script to be executed and I
> haven't seen you provide that.
I gave a bunch of commands which can be copy & pasted into a shell as-is.
> So, again I'm guessing a bit ... the only think I can think of
On 7 Jan 2014, at 18:08, Markus Hitter wrote:
>
> For those on the -dev mailing list, we're talking about this bug:
>
> https://savannah.gnu.org/bugs/?41125#comment0
>
>
> Am 07.01.2014 15:17, schrieb Richard Frith-Macdonald:
>
>> I might guess that the issue you mean [...]
>
> Instead of
For those on the -dev mailing list, we're talking about this bug:
https://savannah.gnu.org/bugs/?41125#comment0
Am 07.01.2014 15:17, schrieb Richard Frith-Macdonald:
> I might guess that the issue you mean [...]
Instead of guessing I'd prefer you'd try with the shell snippets I
provided. They
19 matches
Mail list logo
