Displaying 7 results from an estimated 7 matches for "l101".
Did you mean:
101
2010 Apr 26
2
Never executing loop in smallft.c
...oid drfti1(int n, float *wa, int *ifac){
39 static int ntryh[4] = { 4,2,3,5 };
40 static float tpi = 6.28318530717958648f;
41 float arg,argh,argld,fi;
42 int ntry=0,i,j=-1;
43 int k1, l1, l2, ib;
44 int ld, ii, ip, is, nq, nr;
45 int ido, ipm, nfm1;
46 int nl=n;
47 int nf=0;
48
49 L101:
50 j++;
51 if (j < 4)
52 ntry=ntryh[j];
53 else
54 ntry+=2;
55
56 L104:
57 nq=nl/ntry;
58 nr=nl-ntry*nq;
59 if (nr!=0) goto L101;
...
As far as I can see, nr will always be 0, witch means that j will be
also always 0 and ntry will have only the first value in ntryh.
Is tha...
2024 May 21
1
Default CXXFLAGS
...n R's own /etc/R/Makeconf via a
> programmatic way via some sort of option or alike.
I think this is about the following line in debian/rules:
optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS`
https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101
...which later propagares to cxxflags = $(optimflags) and
eventually CXXFLAGS="$(cxxflags)" ... ./configure.
On Sid, dpkg-buildflags --get CFLAGS includes
-Werror=implicit-function-declaration, which g++ doesn't like:
root at 020af1fe3ba2:/# g++ -Werror=implicit-function-declaratio...
2024 May 21
1
Default CXXFLAGS
On 21 May 2024 at 13:01, Jeroen Ooms wrote:
| Compiling packages with C++ code using the default r-base-dev
| configuration on debian:sid shows a lot of:
|
| cc1plus: warning: '-Werror=' argument
| '-Werror=implicit-function-declaration' is not valid for C++
|
| Can this flag be removed from R CMD config CXXFLAGS?
"No."
That was quoting Simon Urbanek from a few
2024 May 21
1
Default CXXFLAGS
...wing line in debian/rules:
Without having looked in much detail, I guess foer the CXXFLAGS we want
dpkg-buildflags --get CXXFLAGS?
Best
-k
> optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS`
> https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101
> ...which later propagares to cxxflags = $(optimflags) and
> eventually CXXFLAGS="$(cxxflags)" ... ./configure.
> On Sid, dpkg-buildflags --get CFLAGS includes
> -Werror=implicit-function-declaration, which g++ doesn't like:
> root at 020af1fe3ba2:/# g++ -Werror=imp...
2015 May 22
1
nutdrv_qx interface change proposal item_t::preprocess
...ion before quitting the query-preprocess one).
>
> Here's a first try at it:
> https://github.com/zykh/nut/tree/nutdrv_qx_preprocess_command
That would work for me too. I'm looking forward to the merge.
[1]
https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.h#L97-L101
[2]
https://github.com/nickma82/nut/commit/ce330a3873fd0a9243a61258db243a6eee=327e65
2003 Jan 19
1
Applications start with title bar grayed
When I try to start notepad, it starts with a grayed title bar,
like it wasnt active. I cant enter text into the input window.
Strange thing, menus work.
To get it look like active and type text, I must select the system menu
and "About wine".
After closing the new window (that has appeared as active), i see that
notepad appears
active and I can enter text.
Has someone this issue ?
2015 May 01
3
nutdrv_qx interface change proposal item_t::preprocess
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I would like to propose an interface change/extension, in order to be
able to clearly differ from a PRE_SEND and a POST_RECEIVE
item_t->preprocess-ing calls.
IMHO there is no option to differ from item->preprocess(..), called from
[1] and called from [2], at the moment. My idea is to extend the
item_t->preprocess(..) with an additional