On October 30, 2014 9:18:29 PM CDT, Gedare Bloom wrote:
>On Thu, Oct 30, 2014 at 7:13 PM, Chris Johns wrote:
>> On 31/10/2014 6:42 am, Gedare Bloom wrote:
>>>
>>> On Thu, Oct 30, 2014 at 3:40 PM, Gedare Bloom
>wrote:
On Thu, Oct 30, 2014 at 3:32 PM, Chris Johns
>wrote:
>
> H
On Thu, Oct 30, 2014 at 7:13 PM, Chris Johns wrote:
> On 31/10/2014 6:42 am, Gedare Bloom wrote:
>>
>> On Thu, Oct 30, 2014 at 3:40 PM, Gedare Bloom wrote:
>>>
>>> On Thu, Oct 30, 2014 at 3:32 PM, Chris Johns wrote:
Hi,
Libdl tests in the testsuite depend on tools in rtems-to
On 31/10/2014 6:42 am, Gedare Bloom wrote:
On Thu, Oct 30, 2014 at 3:40 PM, Gedare Bloom wrote:
On Thu, Oct 30, 2014 at 3:32 PM, Chris Johns wrote:
Hi,
Libdl tests in the testsuite depend on tools in rtems-tools.git/linkers.
Should I raise a configure error if the tools are not found or not
On Thu, Oct 30, 2014 at 3:40 PM, Gedare Bloom wrote:
> On Thu, Oct 30, 2014 at 3:32 PM, Chris Johns wrote:
>> Hi,
>>
>> Libdl tests in the testsuite depend on tools in rtems-tools.git/linkers.
>> Should I raise a configure error if the tools are not found or not build the
>> tests ?
>>
>> Raising
On Thu, Oct 30, 2014 at 3:32 PM, Chris Johns wrote:
> Hi,
>
> Libdl tests in the testsuite depend on tools in rtems-tools.git/linkers.
> Should I raise a configure error if the tools are not found or not build the
> tests ?
>
> Raising an error is my preferred option because libdl for the supporte
Hi,
Libdl tests in the testsuite depend on tools in rtems-tools.git/linkers.
Should I raise a configure error if the tools are not found or not build
the tests ?
Raising an error is my preferred option because libdl for the supported
archs is tested however it creates a dependency between rt
