similar to: [LLVMdev] Build broken on MSVC 9.0

Hola!! tengo un data.frame donde cada fila corresponde a un año y cada columna a un mes (De enero a diciembre) > head(valT) V2 V3 V4 V5 V6 V7 V8 V9 V10 V11 V12 V13 1941 18.0 16.3 15.2 10.1 8.1 8.3 8.8 9.2 7.9 12.2 11.9 14.6 1942 17.2 15.9 13.6 11.6 8.7 6.2 6.4 7.2 9.7 12.0 14.1 16.7 1943 17.6 17.3 13.5 12.5 10.5 7.0 8.2 7.9 -999.9 -999.9

> also think that Debian did a very stupid thing > when they > gave 'nobody' the ID of '65534', but you just have to work around it. Good point here, i'll drop that also at the debian samba bug list. Totaly forgot about nobody and uid 65534.. In dutch.. "Het kwartje valt...." ( A penny drops.. ) hihi.. But its "it finally makes sense" ...

Am 09.08.09 23:36, schrieb Eli Friedman: > > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. > Please note that the MSVC buildbot only builds the X86 target at the moment. I don't know why though.

On 2009-08-30 03:55, Chris Lattner wrote: > > On Aug 28, 2009, at 1:53 AM, Daniel Dunbar wrote: > >> Nice! >> >> This looks good to me but probably Chris or someone else should sign >> off on it. > > This seems ok to me, please commit. One minor comment: Committed. It would be useful if someone could test if this works on Windows, the msvc buildbot was all

Eli Friedman <eli.friedman at gmail.com> writes: > MSVC *is* continuously checked; see > http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9. Anyone > who breaks the MSVC build will get a nastygram from buildbot. This is new news for me. If the developer who broke the msvc build receives a nastygram, would he urged to fix it when he has no msvc compiler and probably no

On Sun, Aug 9, 2009 at 3:35 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> MSVC *is* continuously checked; see >> http://google1.osuosl.org:8011/builders/clang-i686-xp-msvc9.  Anyone >> who breaks the MSVC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer

I have filed a number of problem reports about getting the LLVM test infrastructure working for an environment with: Windows + MSVC9 + Cmake + NMake makefiles + MKS. (MKS provides unix-like tools for Windows, but based on very old versions, so they have quirky or minimal compatibility with GNU tools.) http://llvm.org/bugs/show_bug.cgi?id=9689 - Fix Cmake generation of compile_cxx for MSVC -

On Sun, Aug 9, 2009 at 1:04 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >>> I think most LLVM users on Windows are interested on X86 only. This >>> saves a lot of time on the build process and creates smaller >>>

Sorry for the rapid fire replies, but this configuration works for me: install(DIRECTORY include/ DESTINATION include # FILES_MATCHING PATTERN "*.def" PATTERN "*.h" PATTERN "*.td" PATTERN "*.inc" PATTERN ".svn" EXCLUDE ) install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/include/ DESTINATION include # FILES_MATCHING PATTERN

On Thu, Sep 30, 2010 at 3:08 PM, Samuel Williams <space.ship.traveller at gmail.com> wrote: > Hi, > > I might just be doing something stupid, but when I do > > $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. > $ sudo make install > > I don't get the expected headers in >        /usr/local/llvm-2.8/include/llvm > > It is

Hi, I might just be doing something stupid, but when I do $ cmake -DCMAKE_INSTALL_PREFIX=/usr/local/llvm-2.8 -DCMAKE_BUILD_TYPE=Release .. $ sudo make install I don't get the expected headers in /usr/local/llvm-2.8/include/llvm It is simply an empty directory. What am I doing wrong? This is on Mac OS X, CMake 2.8+ Kind regards, Samuel