On Tue, Dec 4, 2018 at 4:51 PM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:
> Hello Rick
>
> The official answer fo macOS semaphores
> Is to use Grand Central Dispatch's dispatch_semaphore_t.
>
> If You google with dispatch_semaphore_t
> You will find quite a
I am not getting any compile errors at all on Windows. My best guess is
you're compiling with a back level library, but absent any error
information, that's all I can do.
Rick
On Wed, Dec 5, 2018 at 4:27 PM Håkan Erixon
wrote:
> I expect you test if your commits will pass.
>
>
>
>
>
> *From:*
Google is your friend...here's the first hit I found and there's a lot more
out there.
https://stackoverflow.com/questions/6077414/how-to-set-the-ldflags-in-cmakelists-txt
There are also a few places in the oorexx CMakeList.txt file where linker
flags are set for different configurations.
Rick
I expect you test if your commits will pass.
From: Rick McGuire
Sent: den 5 december 2018 22:19
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Ad shebang, parallel installed ooRexx interpreters
running concurrently (Re: revision 11569, MacOS, question ad shebang
And
On Wed, Dec 5, 2018 at 1:40 PM Rick McGuire wrote:
> I have to be frank here, this is not going to be a problem of just dumping
> an error log into an email and expecting us to fix the problems. You have
> going to have to diagnose any problems involving this environment on your
> own. You are
And yet, you don't include the errors so a fix can be made. I'm not in the
mood for people throwing shade today :-(
Rick
On Wed, Dec 5, 2018 at 4:11 PM Håkan Erixon
wrote:
> Astonished that you will fix problem without a bug report (PASE compile)
> and in the same time complain about other
Astonished that you will fix problem without a bug report (PASE compile) and in
the same time complain about other reports.
FYI can’ t compile latest commit because of rexxutil.cpp for windows changes
From: Rick McGuire
Sent: den 5 december 2018 21:54
To: Open Object Rexx Developer Mailing
On Wed, Dec 5, 2018 at 1:10 PM Rony G. Flatscher
wrote:
> On 05.12.2018 15:08, Rick McGuire wrote:
>
> Seriously, it would be way better to confine your emails to a single topic
> so that all of this stuff does not get propagated in thread replies.
>
> Hmm, thought I keep all related information
I have to be frank here, this is not going to be a problem of just dumping
an error log into an email and expecting us to fix the problems. You have
going to have to diagnose any problems involving this environment on your
own. You are the first person to try this and nobody on this list (that I'm
And just to be complete I DID post a patch to this list:
On Wed, Nov 7, 2018 at 5:01 PM P.O. Jonsson mailto:oor...@jonases.se>> wrote:
Dear Rick and Erich,
I have tried today to build on MAC using revision 11517. Unfortunately the
Shebang comes out as #!/opt/oorexx5.0.0/bin/rexx rather as the
Contrary to what Rick states I proposed the change for CMake for the Mac
section to also use the (IMO correct) Shebang #!usr/bin/env rexx. I did not
provide a patch but a bug report but the proposal was turned down by Rick
because he insisted on a special shebang for Mac, different than the
On Wed, Dec 5, 2018 at 11:01 AM Jack Woehr
wrote:
> Okay, we get pretty far, and then:
>
>
>
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
> information.
> ld: 0711-781 ERROR: TOC overflow. TOC size: 85080 Maximum size: 65536
> collect2: error: ld returned 12
On 05.12.2018 15:08, Rick McGuire wrote:
> Seriously, it would be way better to confine your emails to a single topic so
> that all of this
> stuff does not get propagated in thread replies.
Hmm, thought I keep all related information in one e-mail to ease getting an
overview on the current
Okay, we get pretty far, and then:
[ 67%] Linking CXX shared library bin/librexx.so
ld: 0711-224 WARNING: Duplicate symbol: .SysMutex::create(bool)
ld: 0711-224 WARNING: Duplicate symbol: .SysSemaphore::SysSemaphore(bool)
ld: 0711-224 WARNING: Duplicate symbol: .SysSemaphore::SysSemaphore(bool)
Well, that was fast :)
I'll check out and try again later this morning. Thank ou.
On Wed, Dec 5, 2018 at 8:31 AM Rick McGuire wrote:
> I already committed the fix.
>
>
--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This
I already committed the fix.
On Wed, Dec 5, 2018 at 10:26 AM Jack Woehr
wrote:
> Should I file a bug report?
>
>
> On Wed, Dec 5, 2018 at 7:51 AM Rick McGuire wrote:
>
>> And this is exactly the reason to use 5.0.0, to give us a chance to fix
>> these sort of issues before we go gold.
>>
>> On
Should I file a bug report?
On Wed, Dec 5, 2018 at 7:51 AM Rick McGuire wrote:
> And this is exactly the reason to use 5.0.0, to give us a chance to fix
> these sort of issues before we go gold.
>
> On Wed, Dec 5, 2018 at 9:47 AM Jack Woehr
> wrote:
>
>> Rick, Erich:
>>
>> Had the same idea
And this is exactly the reason to use 5.0.0, to give us a chance to fix
these sort of issues before we go gold.
On Wed, Dec 5, 2018 at 9:47 AM Jack Woehr
wrote:
> Rick, Erich:
>
> Had the same idea about 5.0.0 ... So I tried that ... it bombs looking for
> AF_UNIX ...
> *(In the following, note
Rick, Erich:
Had the same idea about 5.0.0 ... So I tried that ... it bombs looking for
AF_UNIX ...
*(In the following, note that PASE is basically AIX-on-IBMi)*
/home/JWOEHR/work/ooRexx-5/oorexx-code-0/rexxapi/common/platform/unix/SysCSStream.cpp:246:16:
error: 'AF_LOCAL' was not declared in
Seriously, it would be way better to confine your emails to a single topic
so that all of this stuff does not get propagated in thread replies.
On Wed, Dec 5, 2018 at 8:54 AM Rony G. Flatscher
wrote:
> revision 11569, MacOS, all ooRexx test units pass
>
> This time also warnings when running
revision 11569, MacOS, all ooRexx test units pass
This time also warnings when running cmake:
cmake -DCMAKE_BUILD_TYPE=relWithDebInfo ~/dev/oorexx_allura/main/trunk
... cut ...
-- Looking for pwd.h
CMake Warning (dev) at
Jack,
I looks like the ARGUMENT_TYPE issue is also fixed in the 4.2 branch that
Erich pointed out too, but I still recommend you switch to 5.0.0.
Rick
On Tue, Dec 4, 2018 at 9:01 PM Jack Woehr
wrote:
> Please excuse me for persisting :) I'd really like to build some version
> of OORexx on IBM
This is an example where your assumption that starting with 4.2.0 would be
easier is wrong. I believe this problem was encountered sometime ago and
was fixed in the trunk.
Truthfully, you would be better off skipping ahead to 5.0.0. We have
revamped the build system to use CMake, so all of the
23 matches
Mail list logo
