q-lang-users

[q-lang-users] Q 7.11 on Mac OS X

[Ryan S. <rya...@us...>]

Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but 7.11  
doesn't. Here's what it does:


$ sudo port install q
Password:
--->  Fetching q
--->  Verifying checksum(s) for q
--->  Extracting q
--->  Configuring q
--->  Building q with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/_Users_rschmidt_macports_dports_lang_q/work/ 
q-7.11" && make all " returned error 2
Command output: creating clib.la
(cd .libs && rm -f clib.la && ln -s ../clib.la clib.la)
/bin/sh ../../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
DHAVE_CONFIG_H -I. -I../.. -I../../libq  -I/opt/local/include  -O2 - 
MT system.lo -MD -MP -MF .deps/system.Tpo -c -o system.lo system.c
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I../.. -I../../libq -I/opt/ 
local/include -O2 -MT system.lo -MD -MP -MF .deps/system.Tpo -c  
system.c  -fno-common -DPIC -o .libs/system.o
system.c: In function 'ictowcs':
system.c:766: warning: passing argument 2 of 'libiconv' from  
incompatible pointer type
system.c: In function 'icfromwcs':
system.c:787: warning: passing argument 2 of 'libiconv' from  
incompatible pointer type
system.c: In function '__F__system_sys_vars':
system.c:1685: error: 'CLOCK_REALTIME' undeclared (first use in this  
function)
system.c:1685: error: (Each undeclared identifier is reported only once
system.c:1685: error: for each function it appears in.)
system.c:1687: error: 'CLOCK_MONOTONIC' undeclared (first use in this  
function)
system.c:1692: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first  
use in this function)
system.c:1697: error: 'CLOCK_THREAD_CPUTIME_ID' undeclared (first use  
in this function)
system.c: In function '__F__system_process_cpu_clockid':
system.c:5710: error: 'clockid_t' undeclared (first use in this  
function)
system.c:5710: error: parse error before 'id'
system.c:5711: error: 'id' undeclared (first use in this function)
system.c: In function '__F__system_thread_cpu_clockid':
system.c:5727: error: 'clockid_t' undeclared (first use in this  
function)
system.c:5727: error: parse error before 'id'
system.c:5728: error: 'id' undeclared (first use in this function)
system.c: In function '__F__system_iconv':
system.c:6208: warning: passing argument 2 of 'libiconv' from  
incompatible pointer type
make[4]: *** [system.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Status 1 encountered during processing.
$

Re: [q-lang-users] Q 7.11 on Mac OS X

[Albert G. <Dr....@t-...>]

Hi Ryan,

sorry for the long delay, I just returned home from a conference...

Ryan Schmidt wrote:
> system.c:1685: error: 'CLOCK_REALTIME' undeclared (first use in this  
> function)
> system.c:1687: error: 'CLOCK_MONOTONIC' undeclared (first use in this  
> function)
> system.c:1692: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first  
> use in this function)
> system.c:1697: error: 'CLOCK_THREAD_CPUTIME_ID' undeclared (first use  
> in this function)
> system.c: In function '__F__system_process_cpu_clockid':
> system.c:5710: error: 'clockid_t' undeclared (first use in this  
> function)

Yes, this stuff is new, but it should only be included if the
appropriate interfaces are detected during configure and some special
symbols (_POSIX_TIMERS et al) are defined in unicode.h. Maybe this again
needs some special defines on OSX to be enabled? What does 'man
clock_gettime' say?

Cheers,
Albert

-- 
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikinformatik.uni-mainz.de/ag

Re: [q-lang-users] Q 7.11 on Mac OS X

[Ryan S. <rya...@us...>]

On Mar 5, 2008, at 17:31, Albert Graef wrote:

> Ryan Schmidt wrote:
>
>> system.c:1685: error: 'CLOCK_REALTIME' undeclared (first use in this
>> function)
>> system.c:1687: error: 'CLOCK_MONOTONIC' undeclared (first use in this
>> function)
>> system.c:1692: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first
>> use in this function)
>> system.c:1697: error: 'CLOCK_THREAD_CPUTIME_ID' undeclared (first use
>> in this function)
>> system.c: In function '__F__system_process_cpu_clockid':
>> system.c:5710: error: 'clockid_t' undeclared (first use in this
>> function)
>
> Yes, this stuff is new, but it should only be included if the
> appropriate interfaces are detected during configure and some special
> symbols (_POSIX_TIMERS et al) are defined in unicode.h. Maybe this  
> again
> needs some special defines on OSX to be enabled? What does 'man
> clock_gettime' say?

"No manual entry for clock_gettime"

Re: [q-lang-users] Q 7.11 on Mac OS X

[Albert G. <Dr....@t-...>]

Ryan Schmidt wrote:
> "No manual entry for clock_gettime"

Ok, so that probably means that the highres timers aren't available.
Anyway, I've corrected the checks for the availability of these and
various related features, so that they should now properly detect their
absence on OS X, as well as on older Cygwin systems.

Patch is attached. Ryan, could you please check whether this builds ok
now? Sorry for the hassle, I should maybe have pointed you to RC3 so
that we could have checked this before the final release. But I was
pretty sure that OS X would have these, as they've been in POSIX for a
while and AFAIK FreeBSD has them, too.

NOTE to OS X users: What this means for Q programmers on OS X is that
the new highres timers in the system module (Q functions nanotime,
nanosleep etc.) won't be available for that platform. Of course, you can
still use the built-in time and sleep functions, which will
automagically use the best timers available on a system (on Unix systems
without clock_gettime et al this will usually be the C functions
gettimeofday and nanosleep). Alas, these will only work with wall clock
time, whereas the new functions also offer a monotonic clock and
per-process/per-thread cpu clocks. But maybe someone feels inclined to
bug the Darwin developers about implementing clock_gettime and friends,
so that they will work in a future OS X version? ;-)

Cheers,
Albert

-- 
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikinformatik.uni-mainz.de/ag

Re: [q-lang-users] Q 7.11 on Mac OS X

[John C. <co...@cc...>]

Albert Graef scripsit:

> Ryan Schmidt wrote:
> > "No manual entry for clock_gettime"
> 
> Ok, so that probably means that the highres timers aren't available.
> Anyway, I've corrected the checks for the availability of these and
> various related features, so that they should now properly detect their
> absence on OS X, as well as on older Cygwin systems.

I've attached a trivial implementation of clock_gettime that I found in
OpenBSM; it may be useful.

-- 
We call nothing profound                        co...@cc...
that is not wittily expressed.                  John Cowan
        --Northrop Frye (improved)

Re: [q-lang-users] Q 7.11 on Mac OS X

[Albert G. <Dr....@t-...>]

John Cowan wrote:
> I've attached a trivial implementation of clock_gettime that I found in
> OpenBSM; it may be useful.

Thanks a bunch. clock_nanosleep shouldn't be much harder. I'll add those
emulations in the next release. I'll have to think what to do about
clock_getres, though, just assuming 1000 there probably won't be that
useful, do you maybe have some code for that, too?

For the time being, the following Q definitions should also do the trick
(minus the error checking, and it also adds some latency so
nanosleep_until won't be very accurate):

import system;
nanotime _ = round (time*1e9);
nanosleep _ T = sleep (T*1e-9);
nanosleep_until _ T = sleep (T*1e-9-time);

Albert

-- 
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikinformatik.uni-mainz.de/ag

Re: [q-lang-users] Q 7.11 on Mac OS X

[Albert G. <Dr....@t-...>]

Ryan Schmidt wrote:
> Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but 7.11  
> doesn't. Here's what it does:

Hmm, any news on that? Didn't the patch I posted work for you?

Cheers,
Albert

-- 
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr....@t-..., ag...@mu...
WWW:    http://www.musikinformatik.uni-mainz.de/ag

Re: [q-lang-users] Q 7.11 on Mac OS X

[Ryan S. <rya...@us...>]

On Mar 11, 2008, at 3:46 AM, Albert Graef wrote:
> Ryan Schmidt wrote:
>> Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but 7.11
>> doesn't. Here's what it does:
>
> Hmm, any news on that? Didn't the patch I posted work for you?

Sorry for the delay. The patch worked fine, Q 7.11 now compiles, and  
I've updated the port in MacPorts.

Re: [q-lang-users] Q 7.11 on Mac OS X

[Don G. <dg...@cc...>]

I just did selfupdate on MacPorts and list still shows version 7.10.
Anything else I need to do to get 7.11?
--
don


On Apr 18, 2008, at 6:37 PM, Ryan Schmidt wrote:

> On Mar 11, 2008, at 3:46 AM, Albert Graef wrote:
>> Ryan Schmidt wrote:
>>> Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but 7.11
>>> doesn't. Here's what it does:
>>
>> Hmm, any news on that? Didn't the patch I posted work for you?
>
> Sorry for the delay. The patch worked fine, Q 7.11 now compiles, and
> I've updated the port in MacPorts.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> q-lang-users mailing list
> q-l...@li...
> https://lists.sourceforge.net/lists/listinfo/q-lang-users
>

Re: [q-lang-users] Q 7.11 on Mac OS X

[Ryan S. <rya...@us...>]

The portindex only regenerates every 12 hours, so wait a little longer.


On Apr 18, 2008, at 10:08 PM, Don Groves wrote:

> I just did selfupdate on MacPorts and list still shows version 7.10.
> Anything else I need to do to get 7.11?
>
>
> On Apr 18, 2008, at 6:37 PM, Ryan Schmidt wrote:
>
>> On Mar 11, 2008, at 3:46 AM, Albert Graef wrote:
>>> Ryan Schmidt wrote:
>>>> Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but  
>>>> 7.11
>>>> doesn't. Here's what it does:
>>>
>>> Hmm, any news on that? Didn't the patch I posted work for you?
>>
>> Sorry for the delay. The patch worked fine, Q 7.11 now compiles, and
>> I've updated the port in MacPorts.

Re: [q-lang-users] Q 7.11 on Mac OS X

[Don G. <dg...@cc...>]

Ah, thanks.
--
don


On Apr 18, 2008, at 9:37 PM, Ryan Schmidt wrote:

> The portindex only regenerates every 12 hours, so wait a little  
> longer.
>
>
> On Apr 18, 2008, at 10:08 PM, Don Groves wrote:
>
>> I just did selfupdate on MacPorts and list still shows version 7.10.
>> Anything else I need to do to get 7.11?
>>
>>
>> On Apr 18, 2008, at 6:37 PM, Ryan Schmidt wrote:
>>
>>> On Mar 11, 2008, at 3:46 AM, Albert Graef wrote:
>>>> Ryan Schmidt wrote:
>>>>> Hello. Q 7.10 compiled just fine on Mac OS X 10.4.11 Intel, but
>>>>> 7.11
>>>>> doesn't. Here's what it does:
>>>>
>>>> Hmm, any news on that? Didn't the patch I posted work for you?
>>>
>>> Sorry for the delay. The patch worked fine, Q 7.11 now compiles, and
>>> I've updated the port in MacPorts.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> q-lang-users mailing list
> q-l...@li...
> https://lists.sourceforge.net/lists/listinfo/q-lang-users
>