Am 05.01.20 um 17:03 schrieb Paul Smith:
That is not the right URL; you want git://git.sv.gnu.org/gnulib (note the
/git subdirectory is removed).
When you use https: you need to use /git/gnulib after the hostname, but
when you use the git: protocol you just use /gnulib after the hostname.
Ups
On Sun, 2020-01-05 at 12:12 +0100, Christof Warlich wrote:
> Thus, everything looks perfectly fine so far. But the following still
> fails:
>
> > $ git ls-remote git://git.sv.gnu.org/git/gnulib
> > fatal: remote error: access denied or repository not exported:
> > /git/gnulib
That is not the righ
Am 04.01.20 um 21:55 schrieb Paul Smith:
Hm, this worked fine for me:
$ git ls-remote git://git.sv.gnu.org/gnulib
...list of branches...
Perhaps your system is sequestered behind some sort of firewall that will
not allow the git: protocol (port 9418 IIRC) to pass through? Almost all
f
On Sat, 2020-01-04 at 10:16 +0100, Christof Warlich wrote:
> The original doesen't work from my system (Debian Buster) at least:
>
> > $ ./bootstrap
> > ./bootstrap: Bootstrapping from checked-out make sources...
> > ./bootstrap: getting gnulib files...
> > Cloning into 'gnulib'...
> > fatal: unab
Am 03.01.20 um 21:25 schrieb Paul Smith:
On Fri, 2020-01-03 at 20:42 +0100, Christof Warlich wrote:
By the way, I stumbled into a minor issue entirely unrelated to the
feature above that you may want to fix: The gnulib git repository
referenced in bootstrap seems to have changed its location, s
On Fri, 2020-01-03 at 20:42 +0100, Christof Warlich wrote:
> By the way, I stumbled into a minor issue entirely unrelated to the
> feature above that you may want to fix: The gnulib git repository
> referenced in bootstrap seems to have changed its location, so you may
> want it to change it accord
Hi Paul,
Am 03.01.20 um 18:24 schrieb Paul Smith:
Hi Christof; .EXTRA_PREREQS is provided in 4.2.93 please test in your
environment.
Note that I did rework some things to allow it to work with implicit rules
(previously it only worked for explicit rules) although it still can't be
used as a pat
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
> attached is the comprehensive (and significantly reworked) patch that
> implements the feature of a new internal variable
Hi Christof; .EXTRA_PREREQS is provided in 4.2.93 please test in your
environment.
Note that I did rework some thi
Am 14.08.19 um 20:31 schrieb Paul Smith:
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
From my perspective, everything is complete and works as it should,
so I would definitely need your feedback if there is anything missing
or wrong.
Otherwise (or in parallel), could you guide
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
> From my perspective, everything is complete and works as it should,
> so I would definitely need your feedback if there is anything missing
> or wrong.
>
> Otherwise (or in parallel), could you guide me to get the copyright
> assignment
Am 13.07.19 um 14:46 schrieb Paul Smith:
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
Am 10.07.19 um 14:44 schrieb Paul Smith:
Let me know how you want to proceed.
As I want to tackle the most challenging part first, I'd like to suggest to
do the copyright assignment after the t
Am 13.07.19 um 14:46 schrieb Paul Smith:
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
Am 10.07.19 um 14:44 schrieb Paul Smith:
Let me know how you want to proceed.
As I want to tackle the most challenging part first, I'd like to suggest to
do the copyright assignment after the t
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
> Am 10.07.19 um 14:44 schrieb Paul Smith:
> > Let me know how you want to proceed.
>
> As I want to tackle the most challenging part first, I'd like to suggest to
> do the copyright assignment after the technical side is in a decent shape
Am 10.07.19 um 14:44 schrieb Paul Smith:
Would it really help if I try to supply a patch that implements your idea?
Or is the current "state of affairs" sufficient that the general idea (i.e.
allowing to add target specific prerequisites without changing automatic
variables) will eventually go i
On Wed, 2019-07-10 at 10:24 +0200, Christof Warlich wrote:
> > What if we do this instead: create a variable which can contain a list
> > of "hidden prerequisites": they will always be built first but they
> > won't cause any changes in the automatic variables. If set globally it
> > will apply to
Am 09.07.19 um 20:51 schrieb David Boyce:
I don't claim to know much about how Savannah works but I see
anonymous bug reports and RFEs come in frequently so it seems you
don't need a login to make one.
https://www.gnu.org/software/make/manual/html_node/Bugs.html
Thanks, that's want I was looki
Am 09.07.19 um 20:52 schrieb Paul Smith:
https://savannah.gnu.org/bugs/?func=additem&group=make
You don't have to make an account in order to file a bug, but be sure
to add yourself to mail notifications if you don't create an account,
or you won't get any updates.
Ok, but considering your sugg
On Tue, 2019-07-09 at 20:19 +0200, Christof Warlich wrote:
> Am 09.07.19 um 15:42 schrieb David Boyce:
> > I also think the proposal is reasonable but I think it would be
> > "stickier", i.e. less likely to get lost, if you filed it as an
> > enhancement request via the Savannah bug reporting syste
I don't claim to know much about how Savannah works but I see anonymous bug
reports and RFEs come in frequently so it seems you don't need a login to
make one.
https://www.gnu.org/software/make/manual/html_node/Bugs.html
On Tue, Jul 9, 2019 at 11:19 AM Christof Warlich wrote:
> Am 09.07.19 um 1
Am 09.07.19 um 15:42 schrieb David Boyce:
I also think the proposal is reasonable but I think it would be
"stickier", i.e. less likely to get lost, if you filed it as an
enhancement request via the Savannah bug reporting system.
I'd be glad to do that if it increases the chance to get it in. Bu
I also think the proposal is reasonable but I think it would be "stickier",
i.e. less likely to get lost, if you filed it as an enhancement request via
the Savannah bug reporting system.
On Tue, Jul 9, 2019 at 5:27 AM Tim Murphy wrote:
> I quite like this idea because so many of us work on integ
I quite like this idea because so many of us work on integrating things
that we have no permission to modify and we need ways to make them work
cleanly without messing them up. They are sort of "fix-up" or "patch"
dependencies. I'm not sure the name makes this clear though.
Regards,
Tim
On Sat
on 05.07.19 at 23:44 Martin Dorey wrote:
... Sadly, though, adding all these things to the dependency list
won't really help me. We installed this system just three days ago,
yet the mtime on stdio.h is months ago:
devadmin@ch-ep1-3:~$ ls -l /usr/include/stdio.h
-rw-r--r-- 1 root root 31494 Fe
> The target certainly also depends on the compiler frontend, the linker
> backend and the Makefile itself
It's unimaginable that it doesn't depend on compiler libraries and myriad
compiler-provided header files too. Using header files in a compilation
example would make the $(filter ...) solu
24 matches
Mail list logo
