Dear Steffan,
On Fri, Dec 4, 2015 at 2:20 AM, Staffan Larsen
wrote:
> Why is it a problem having executables and libraries in the same
> directory? It was a design choice we made to make things simpler.
It is a consistency problem. There would be no problem if this was the
common case, but it
Why is it a problem having executables and libraries in the same directory? It
was a design choice we made to make things simpler.
/Staffan
> On 3 dec. 2015, at 18:13, Carsten Varming wrote:
>
> Dear David,
>
> I think I finally understand what is going on now. :)
>
> The command "make build
Carsten,
I'll file a RFE for jtreg for you.
-- Jon
On 12/03/2015 09:13 AM, Carsten Varming wrote:
Dear David,
I think I finally understand what is going on now. :)
The command "make build-test-hotspot-jtreg-native" populates
$(OUTPUTDIR)/support/test/hotspot/jtreg/native/lib/ with ".so" fil
Dear David,
I think I finally understand what is going on now. :)
The command "make build-test-hotspot-jtreg-native" populates
$(OUTPUTDIR)/support/test/hotspot/jtreg/native/lib/ with ".so" files using
sub-directories of $(OUTPUTDIR)/support/test/hotspot/jtreg/native/support/
as scratch space for
On 2015-12-03 08:15, David Holmes wrote:
Thanks for that. Tracing through these makefile macros is far too
painful. I wish there were some way to see what they looked like once
expanded.
In the debug log, you get the calls to each macro listed, which can help
to see how it was actually ca
cc'ing build-dev
On 2/12/2015 1:28 AM, Carsten Varming wrote:
Dear David,
See inline.
On Tue, Dec 1, 2015 at 2:26 AM, David Holmes mailto:[email protected]>> wrote:
Hi Carsten,
On 1/12/2015 8:21 AM, Carsten Varming wrote:
Dear Ioi,
Absolutely,
diff -r
