gcc and updates of packages in core
Hello, I tried to build zathura and gimp and it didn't work. But if I try with gcc 4.9.2 I can build them without a problem. I still don't know crux very well, but I'm almost sure it's related to the release cycle of crux but I can't find the information. So my questions are: - When a new version of crux is released, some collections are updated. I think core, opt and xorg. Other ones ? And before the release, the ports are not updated, only if there is an update in the same branch. I mean gcc has been updated from 4.8.3 to 4.8.4. - If my assumption is right, what is the best option when a package in core need an update ? To write a local port ? Thank you! Best regards, Cédric
On Sun, Apr 12, 2015 at 08:12:39PM +0200, Cédric wrote:
Hello,
I tried to build zathura and gimp and it didn't work. But if I try with gcc 4.9.2 I can build them without a problem. I still don't know crux very well, but I'm almost sure it's related to the release cycle of crux but I can't find the information.
It sounds very strange to have build issues in an older gcc version. It's usually the other way around. Gimp builds just fine for me with 4.8.4. I'd suspect some other cause of your build errors.
So my questions are:
- When a new version of crux is released, some collections are updated. I think core, opt and xorg. Other ones ? And before the release, the ports are not updated, only if there is an update in the same branch. I mean gcc has been updated from 4.8.3 to 4.8.4.
We generally *try* (don't laugh!) to hold back breaking changes during the lifetime of a release. Some breaking changes do crop up every once in a while - new deps are currently not handled at all in "# prt-get sysup". Other examples are major'ish xorg updates that break abi and requires driver rebuilds. Typical examples of stuff we hold back are often toolchain related or ports that break a lot of stuff (libpng was held back for this reason prior to crux 3.1). tl;dr: gcc will stay at 4.8.X in crux 3.1. When the CRUX monkeys decide its time for a new release, a new branch will be created for core,opt,xorg and incompatible changes will only be committed to those branches.
- If my assumption is right, what is the best option when a package in core need an update ? To write a local port ?
Yes, a local port is the right answer if you're adventurous. Though in your case im convinced something else is wrong.
Thank you!
Best regards,
Cédric
-- Fredrik Rinnestam - monkey at large
Hello Cédric, On Wed, Apr 15, 2015 at 7:55 AM, Fredrik Rinnestam <fredrik@rinnestam.se> wrote:
On Sun, Apr 12, 2015 at 08:12:39PM +0200, Cédric wrote:
I tried to build zathura and gimp and it didn't work. But if I try with gcc 4.9.2 I can build them without a problem. I still don't know crux very well, but I'm almost sure it's related to the release cycle of crux but I can't find the information.
It sounds very strange to have build issues in an older gcc version. It's usually the other way around. Gimp builds just fine for me with 4.8.4. I'd suspect some other cause of your build errors.
Perhaps pasting the exact error would be useful here, especially because the compiler may not be responsible. Ryan
Hello, thank you very much for your answers.
When the CRUX monkeys decide its time for a new release, a new branch will be created for core,opt,xorg and incompatible changes will only be committed to those branches.
Yes, a local port is the right answer if you're adventurous. Though in your case im convinced something else is wrong.
After this problem I had time to think to my switch to Crux. As you say, probably there is another problem for gimp, but for sure the problem with zathura has to do with the version of gcc. I think I better have to keep a distribution with rolling release. My switch is not finished and I already see some troubles. Thank you for all your help! Regards, Cédric
On Thu, 16 Apr 2015 22:33:30 +0200 Cédric wrote:
After this problem I had time to think to my switch to Crux. As you say, probably there is another problem for gimp, but for sure the problem with zathura has to do with the version of gcc. I think I better have to keep a distribution with rolling release. My switch is not finished and I already see some troubles.
Girara/zathura build just fine here (using ports from bdfy repo). Pedja
participants (4)
-
Cédric -
Fredrik Rinnestam -
Predrag Ivanovic -
Ryan Mullen