the alloc statement coimes from the guide.

I try some of the variations

Am 20.06.20 um 14:19 schrieb Matthias Seidel:
Hi,

See comment inside. Maybe this solves it.

Am 20.06.20 um 14:12 schrieb Peter Kovacs:
Right. Sorry.

My switches:

./configure \
     --with-dmake-path=${HOME}/dmake/bin/bin/dmake \
      --with-epm=${HOME}/epm/bin/bin/epm \
     --with-lang="${LANGS}" \
     --with-jdk-home=${jdkhome} \
     --with-package-format="installed" \
     --with-vendor="Petko Testbuild"\
     --with-build-version="aoo4ever-$(date +"%Y-%m-%d %H:%M") - `uname
-sm`\n ${GitHash}" \
     --enable-crashdump=yes \
     --enable-category-b \
     --enable-beanshell \
     --enable-wiki-publisher \
     --enable-bundled-dictionaries \
     --enable-opengl  \
     --enable-dbus  \
     --without-junit \
     --without-stlport \
     --disable-odk \
     --without-fonts \
     --disable-systray \
     --with-alloc=internal \
--with-alloc            Define which allocator to build with
                           (choices are oo, system, tcmalloc, jemalloc)

                           Note that on FreeBSD/NetBSD system==jemalloc
     --enable-verbose \
     --with-openldap \

Am 20.06.20 um 14:01 schrieb Matthias Seidel:
Hi Peter,

Am 20.06.20 um 13:56 schrieb Peter:
Hi,


When Running configure ion Mac OS X I get the error Message:

checking whether we are cross compiling... configure: error: in
`workspace/AOO/gitbox/main':
configure: error: cannot run C compiled programs.
If it is a "configure: error:" you should probably post your used
configure switches...

Otherwise we have to simply guess... ;-)

Regards,

    Matthias


I have Xcode installed, and the commandline tools are also
installed. Any other Ideas how to solve this?



---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
For additional commands, e-mail:[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to