[DiscordArchive] Well lets ask this. What version of linux are you using?
[DiscordArchive] Well lets ask this. What version of linux are you using?
Original source
Yes, I'm already up to date and was planning on upgrading, but not so quickly and early, but now you're forced to keep your server up to date.
rektbyfaith
05-05-2024, 06:44 PM #21Archived author: Krutok • Posted: 2024-05-05T18:44:35.329000+00:00
Original source
Yes, I'm already up to date and was planning on upgrading, but not so quickly and early, but now you're forced to keep your server up to date.
Original source
Tragic
rektbyfaith
05-05-2024, 06:49 PM #22Archived author: Bench • Posted: 2024-05-05T18:49:50.557000+00:00
Original source
Tragic
Original source
Originally my VPS server was a Debian 10 server, so I've already completed a dist upgrade, which will now be the second one. It's not that difficult to upgrade.^^
rektbyfaith
05-05-2024, 06:50 PM #23Archived author: Krutok • Posted: 2024-05-05T18:50:24.647000+00:00
Original source
Originally my VPS server was a Debian 10 server, so I've already completed a dist upgrade, which will now be the second one. It's not that difficult to upgrade.^^
Original source
Nobody says that, but I don't look at the wiki every day. I just pulled the latest files from Github as normal and suddenly I get an error like this.
It would be nice if the changes on github stated that an OS is being replaced and another OS is no longer supported, so that you avoid surprises. I'm also not a fan of old versions, but as I said it would have been nice if there had been a note there.
rektbyfaith
05-05-2024, 07:02 PM #24Archived author: Krutok • Posted: 2024-05-05T19:02:02.650000+00:00
Original source
Nobody says that, but I don't look at the wiki every day. I just pulled the latest files from Github as normal and suddenly I get an error like this.
It would be nice if the changes on github stated that an OS is being replaced and another OS is no longer supported, so that you avoid surprises. I'm also not a fan of old versions, but as I said it would have been nice if there had been a note there.
Original source
I've said it before (but not to you) that this is a special case that is undetected only for clang users on linux (mac is unaffected)
rektbyfaith
05-05-2024, 07:03 PM #25Archived author: Tea • Posted: 2024-05-05T19:03:21.522000+00:00
Original source
I've said it before (but not to you) that this is a special case that is undetected only for clang users on linux (mac is unaffected)
Original source
the real requirement is a dependency that is installed together with gcc - we cannot detect in cmake
rektbyfaith
05-05-2024, 07:03 PM #26Archived author: Tea • Posted: 2024-05-05T19:03:58.844000+00:00
Original source
the real requirement is a dependency that is installed together with gcc - we cannot detect in cmake
Original source
I do not know your level of linux knowledge and because I've seen people report that they still had errors even after they upgraded gcc on their debian 11, we switched from recommending "upgrade gcc" to "upgrade os"
rektbyfaith
05-05-2024, 07:05 PM #27Archived author: Tea • Posted: 2024-05-05T19:05:45.360000+00:00
Original source
I do not know your level of linux knowledge and because I've seen people report that they still had errors even after they upgraded gcc on their debian 11, we switched from recommending "upgrade gcc" to "upgrade os"
Original source
I don't want to blame you now, but it would be very nice to point out to Github, because as a Linux user you know that if errors occur now, it could be due to the OS no longer being supported.
When a fatal error like this appears to me, I first assume that what is wrong in the code is not correct, but that it is the OS itself and the GCC version.
rektbyfaith
05-05-2024, 07:08 PM #28Archived author: Krutok • Posted: 2024-05-05T19:08:00.057000+00:00
Original source
I don't want to blame you now, but it would be very nice to point out to Github, because as a Linux user you know that if errors occur now, it could be due to the OS no longer being supported.
When a fatal error like this appears to me, I first assume that what is wrong in the code is not correct, but that it is the OS itself and the GCC version.
Original source
but what about https://github.com/TrinityCore/TrinityCo...604ab6cb29 ? does that not count (same commit in all branches)
[Embed: Build: Update required GCC version to 11.1 · TrinityCore/TrinityCor...]
https://github.com/TrinityCore/TrinityCo...604ab6cb29
rektbyfaith
05-05-2024, 07:08 PM #29Archived author: Tea • Posted: 2024-05-05T19:08:54.809000+00:00
Original source
but what about https://github.com/TrinityCore/TrinityCo...604ab6cb29 ? does that not count (same commit in all branches)
[Embed: Build: Update required GCC version to 11.1 · TrinityCore/TrinityCor...]
https://github.com/TrinityCore/TrinityCo...604ab6cb29
Original source
General rule, no matter what: always use latest stable software. No matter in what scenario. Waiting for eol and other related things is something people still have to learn not to do. Solves many problems in many projecst
rektbyfaith
05-05-2024, 07:09 PM #30Archived author: Fabian • Posted: 2024-05-05T19:09:55.491000+00:00
Original source
General rule, no matter what: always use latest stable software. No matter in what scenario. Waiting for eol and other related things is something people still have to learn not to do. Solves many problems in many projecst
1 Guest(s)
1 Guest(s)