search for: timey

I have two data frames of flight data, but they have very different numbers of rows. They come from different sources, so the data are not identical. > names(oooi) [1] "FltOrigDt" "MkdCrrCd" [3] "MkdFltNbr" "DprtTrpnStnCd" [5] "ArrTrpnStnCd" "ActualOutLocalTimestamp"

...autoconf + makefiles > > now that 3.3 has branched? > +1. > - CMake is not available everywhere. Bourne shells are*. > > As I recall, this is the reason autoconf generates shell scripts: because > nearly every operating system out there comes with a shell! Even the > old-timey MPW development environment for the Mac came with one! (* Even > Windows comes with a shell, though it's not a Bourne shell but something > else entirely with a few constructs borrowed from the Bourne shell's > predecessor, the Thompson shell. But I only care about Windows inasmuch...

...lbeit a clumsy workaround). Just something to keep in mind if and when you do move to CMake. - CMake is not available everywhere. Bourne shells are*. As I recall, this is the reason autoconf generates shell scripts: because nearly every operating system out there comes with a shell! Even the old-timey MPW development environment for the Mac came with one! (* Even Windows comes with a shell, though it's not a Bourne shell but something else entirely with a few constructs borrowed from the Bourne shell's predecessor, the Thompson shell. But I only care about Windows inasmuch as people stil...

...al" - does that mean we don't need a supporting GCC installation > anymore? What do we do to enable this feature? Would our flags above need > to change if we do that? > > On the runtime side, clang/llvm generated a bunch of calls to floating > point functions that our old-timey gcc library didn't contain - > specifically __floatundidf and __floatundisf and a couple of other > similarly named routines. We managed to get them out of a newer libgcc, > but couldn't find anything in clang/llvm that had them. I found them in > compiler-rt, but from what I...

...on is functional" - does that mean we don't need a supporting GCC installation anymore? What do we do to enable this feature? Would our flags above need to change if we do that? > > On the runtime side, clang/llvm generated a bunch of calls to floating point functions that our old-timey gcc library didn't contain - specifically __floatundidf and __floatundisf and a couple of other similarly named routines. We managed to get them out of a newer libgcc, but couldn't find anything in clang/llvm that had them. I found them in compiler-rt, but from what I gather that doesn...

...ode emission is functional" - does that mean we don't need a supporting GCC installation anymore? What do we do to enable this feature? Would our flags above need to change if we do that? On the runtime side, clang/llvm generated a bunch of calls to floating point functions that our old-timey gcc library didn't contain - specifically __floatundidf and __floatundisf and a couple of other similarly named routines. We managed to get them out of a newer libgcc, but couldn't find anything in clang/llvm that had them. I found them in compiler-rt, but from what I gather that doesn...

Hi All, I fear starting another centi-thread on this but I'll give it a shot. We're currently supporting two build systems which is definitely one more than we (or I) want to support. I don't know of any support in autoconf past the --host/--build/--target case that's not supported in cmake. I'll send out an assertion here that this support isn't necessary and any system