Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15009 > unrolled thread
| Started by | Vladimir Marek <Vladimir.Marek@oracle.com> |
|---|---|
| First post | 2018-12-30 14:37 +0100 |
| Last post | 2018-12-30 14:37 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: The usage of `cd builtins && $(MAKE) ...` Vladimir Marek <Vladimir.Marek@oracle.com> - 2018-12-30 14:37 +0100
| From | Vladimir Marek <Vladimir.Marek@oracle.com> |
|---|---|
| Date | 2018-12-30 14:37 +0100 |
| Subject | Re: The usage of `cd builtins && $(MAKE) ...` |
| Message-ID | <mailman.6558.1546177074.1284.bug-bash@gnu.org> |
Hi, > I see things like `cd builtins && $(MAKE) ...` in the Makefiles in > bash source code. GNU Make has the option of -C for entering a > directory and make. Is the reason to cd then make for compatibility > with other make's that don't support -C? Thanks. I'm afraid that you are in wrong mailing list. I'm putting this list on bcc. You can consider asking at one of autotools lists https://www.lrde.epita.fr/~adl/autotools.html I would choose automake one. But yes, I believe that it's because not every make clone has -C. Cheers -- Vlad
Back to top | Article view | gnu.bash.bug
csiph-web