Re: cannot install watchman?

On 11/25/22, 5:24 AM, "Hanspeter Niederstrasser" <[email protected]> wrote:

    On 11/25/22 1:26 AM, Daniel Macks wrote:
    > On 11/20/22, 9:01 AM, "Hanspeter Niederstrasser" <[email protected]> wrote:
    >>
    >      > Our watchman is pretty old, but even the immediate next release
    >      > completely changes the build system and adds many dependencies that we
    >      > don't have, some of which might be impossible(?).
    > 
    >      I made some progress on some deps for upgrading watchman, but one
    >      library folly [1] wasn't working. Maybe someone will have better luck
    >      with it.
    > 
    >      [1] https://github.com/facebook/folly
    > 
    > I pushed a few new packages that folly required a dependencies (enough to get through 'cmake'), but compiling fails on my 10.13 box with some typedef errors in Time.h. Applying a fix for them, analogous to https://github.com/facebook/folly/pull/488 , gave a bunch of warnings on that section of code but no errors.
    > 
    > Next up, a bunch of asm errors:
    > 
    > /tmp/foo/folly/synchronization/AtomicUtil-inl.h:279:1: error: invalid output
    >        constraint '=@ccc' in asm
    > FOLLY_DETAIL_ATOMIC_BIT_OP_DEFINE(bts);
    > ^
    > /tmp/foo/folly/synchronization/AtomicUtil-inl.h:240:17: note: expanded from
    >        macro 'FOLLY_DETAIL_ATOMIC_BIT_OP_DEFINE'
    >                : "=@ccc"(out), "+m"(*ptr)                                  \
    >                  ^
    > 
    > Seems like I need a newer compiler than the clang-10.0.0 that comes with xcode-10.1. MacPorts says it's a minimum OS X 10.14 (https://trac.macports.org/ticket/65306). Switching to fink's gcc11 (bin/g++-fsf-11) seems to get me past those, to a compiled libfolly.a. But a final linking stage fails:
    > 
    > [ 99%] Linking CXX executable logging_example
    > ld: library not found for -lc++fs
    > 
    > I don't have libc++fs.{a,dylib} anywhere on my system.

    Can it be patched to use libstdc++fs.a instead?
    $ locate c++fs
    /sw/lib/gcc11/lib/libstdc++fs.a
    /sw/lib/gcc11/lib/libstdc++fs.la
    /sw/lib/gcc12/lib/libstdc++fs.a
    /sw/lib/gcc12/lib/libstdc++fs.la

Using  that, or simply removing the unresolved -lc++* flags, gives the same result: a mile of symbol-not-found errors, such as:

std::__1::ios_base::clear(unsigned int)
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__init(char const*, unsigned long, unsigned long)

Unfortunately I'm voodoo-debugging here:(

dan





_______________________________________________
Fink-users mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users