Hello CRUX maintainers, our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain. To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now: - gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22 - binutils 2.18.50 To minimize the hassle you can use the bootstraped binaries from [2]. Most of the core-ports builds just fine, simple patches are needed for coreutils, gzip and perl, see [1], haven't checked any opt-port for now. Question is how to proceed, I think we have the options to make a update-only release within a short timeframe or put more new, fancy stuff (which one?) in it and, of course, do nothing. Please comment. best regards Juergen [1] http://jue.li/crux/ports/ [1] http://crux.nu/~jue/tmp/ -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Juergen Daubert [2007-08-17 19:26]: Hi Juergen,
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one.
I had this on my list for a few weeks now, too.
Question is how to proceed, I think we have the options to make a update-only release within a short timeframe or put more new, fancy stuff (which one?) in it and, of course, do nothing. Please comment.
Originally I had hoped to finally be able to include texinfo in the next release, but since that depends on pkgutils extensions I think it won't go in yet. So, a simple updated-toolchain-release sounds good to me. However, I'd like to include Xorg 7.3 in the next release. The planned release date for that is 2007-08-29 (which probably means it should be out sometime in September). Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
On Fri, Aug 17, 2007 at 07:26:29PM +0200, Juergen Daubert wrote:
Hello CRUX maintainers,
Hey,
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain.
[..]
Question is how to proceed, I think we have the options to make a update-only release within a short timeframe or put more new, fancy stuff (which one?) in it and, of course, do nothing. Please comment.
Apart from the toolchain / kernel updates, I'd like to see some additional work for 2.4. Full UTF-8 support comes out of my mind (see our tracker); I lack some knowledge on this matter so I'm not sure if some config option is enough or rather we have to ensure all the ports supports UTF-8 where available. I also vote for xorg 7.3 (more in my reply to Tilman's post). Time permitting, I think merging with Matt's livecd would be great, maybe together with a simple remote install option. We can just leave this out if it turns out too time consuming, I prefer to put out a release sooner than later as you seem to support. I suggest we write in this thread what we'd like to add to next release, vote / discuss if needed and move the results to the wiki or better to the bug tracker: - UTF-8 X - Xorg 7.3 X - LiveCD X Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess. Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
Simone Rota [2007-08-17 22:09]:
Full UTF-8 support comes out of my mind (see our tracker); I lack some knowledge on this matter so I'm not sure if some config option is enough or rather we have to ensure all the ports supports UTF-8 where available.
This isn't as straight forward as I had thought: If you set LESSCHARSET to UTF-8 so it can properly display your files, some man pages will look strange (e.g. the list bullets in prt-get(8)). Jesse pointed me to the fix to that. It's a one-line fix in /etc/man.conf: -NROFF /usr/bin/nroff -Tlatin1 -mandoc -c +NROFF /usr/bin/nroff -mandoc -c Note that this is the point where you definitely need a UTF-8 capable font, otherwise (again), man pages will look strange in a few places. ... but that doesn't seem to be a guarantee still, since gcc(1) has issues even when displayed with Bitstream Vera or Terminus (which should work I think!) I'll look into it further.
Time permitting, I think merging with Matt's livecd would be great, maybe together with a simple remote install option. We can just leave this out if it turns out too time consuming, I prefer to put out a release sooner than later as you seem to support.
Agreed. Matt has asked for testing of his netinstall ISO for a few times on IRC, but I still didn't give it a shot. Matt, do you want to publish the URLs here so we can get a wider audience to test it? :D
I suggest we write in this thread what we'd like to add to next release, vote / discuss if needed and move the results to the wiki or better to the bug tracker:
- UTF-8 X - Xorg 7.3 X - LiveCD X
Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess.
Sounds good to me. - UTF-8 X (level of support might vary) - Xorg 7.3 X - LiveCD X - Netinstall X (if it can be ready by release time) Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Tilman Sauerbeck wrote: [...]
Matt, do you want to publish the URLs here so we can get a wider audience to test it? :D [...]
Certainly. The machine with which I build the updated ISOs is currently powered off at home and I'm at work, so I'll upload this evening. If I were to bootstrap on another machine it would take as long as it would for me to wait out the work day. :) Anyway, I'll reply and post the link here when that's done. The network install is more or less "ready to go", I've been using it in some form or other since CRUX 2.1. By that I mean it works great for me but I certainly haven't tested every possible scenario. It could benefit from a new feature or two like proxy support (which it does technically support because it simply uses wget; setting the appropriate env vars works but a prompt in net-setup would look nicer) or manual specification of the kernel version to download, etc. --- As for the rest of this thread, I agree with everything said so far in terms of things that would be nice to see for 2.4, with the small exception that I have no opinion on the UTF-8 issue due to lack of exposure/education. If it's something we need, great. If not, a wiki howto article or the like would be perfect. Matt
On Mon, 2007-08-20 at 09:24 -0500, Matt Housh wrote: [...] Uploaded the ISOs here: http://jaeger.morpheus.net/linux/crux/files/updated-crux-iso/ - both the regular 2.3 and netinst are there. If you want to see the sources, check here: https://secure.morpheus.net/trac/crux-iso/browser/trunk/ Matt
On Fri, Aug 17, 2007 at 10:09:14PM +0200, Simone Rota wrote:
On Fri, Aug 17, 2007 at 07:26:29PM +0200, Juergen Daubert wrote:
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain. Yes, that's indeed a good idea. Toolchain and kernel updates sounds good to me.
Full UTF-8 support comes out of my mind (see our tracker); I lack some knowledge on this matter so I'm not sure if some config option is enough or rather we have to ensure all the ports supports UTF-8 where available. But I am not sure on this point. I've tried to switch to UTF-8 on my personal system some time ago and I had some problems, for example, applications which don't support UTF-8. In the end I've decided to stay with the old charset. It would be nice to get some experiences from people who have successfully switched to UTF-8 yet. Who of you have done this already? Did you have problems?
I also vote for xorg 7.3 (more in my reply to Tilman's post). I vote for that, too.
Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess. That's a really good idea, especially if you look at debian and it's sarge release. :-)
Regards Simon
On Fri, Aug 17, 2007 at 10:09:14PM +0200, Simone Rota wrote: [...l]
Apart from the toolchain / kernel updates, I'd like to see some additional work for 2.4.
- UTF-8 X vote: 0
That's ok for me, but I don't see any improvement making it the default. Most people don't need it, and there are still some apps which are not UTF-8 ready, e.g. aterm or mc. Adding a wiki page how to switch to UTF-8 might be more helpful. And, of course, applications should be build with wide-charcater support if possible.
- Xorg 7.3 X vote: +1
- LiveCD X vote: +1
Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess. ok
regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
On 16:07 Mon 20 Aug?, Juergen Daubert wrote:
On Fri, Aug 17, 2007 at 10:09:14PM +0200, Simone Rota wrote:
[...l]
Apart from the toolchain / kernel updates, I'd like to see some additional work for 2.4.
- UTF-8 X vote: 0
That's ok for me, but I don't see any improvement making it the default. Most people don't need it, and there are still some apps which are not UTF-8 ready, e.g. aterm or mc. Adding a wiki page how to switch to UTF-8 might be more helpful. And, of course, applications should be build with wide-charcater support if possible.
- Xorg 7.3 X vote: +1
- LiveCD X vote: +1
Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess. ok
regards Juergen
#include <standard_Im_not_a_dev_disclaimer.h> I'd like to see the addition/re-addition of some stuff in 2.4 that I feel would be very useful for various people. In no particular order: - gnuparted; for those who can't part with other, inferior operating systems, also handy in rescue situations. - vwdial; Why did this get dropped of the iso? Apparently we still have some users relying on dial-up, or at least we had - until they tried upgrading to 2.3. - libdevmapper Another, more debatable point is the use of a more standard adherent shell as the default, with the removal of bashisms from the rc scripts as an addon. I've used dash quite successfully in the past for this, which is also used by debian/*buntu. It's a lot faster and smaller than bash, however, if used as /bin/sh it will trigger misbehaviour from broken software that assumes /bin/sh == /bin/bash. So far I've only heard of cdega having this issue though - I've come across nothing that complained so far myself (fwiw). cheers //treach -- Don't take life too seriously; you'll never get out of it alive. - Elbert Hubbard
treach [2007-08-22 17:39]:
Another, more debatable point is the use of a more standard adherent shell as the default, with the removal of bashisms from the rc scripts as an addon.
I've used dash quite successfully in the past for this, which is also used by debian/*buntu. It's a lot faster and smaller than bash, however, if used as /bin/sh it will trigger misbehaviour from broken software that assumes /bin/sh == /bin/bash. So far I've only heard of cdega having this issue though - I've come across nothing that complained so far myself (fwiw).
+1, I like the idea of removing bashisms from the RC scripts. Any objections? :p However, I'm not sure whether it's a good idea to start doing a /bin/sh switch now, ie shortly before release preparations begin. However, we could: * make the scripts sh compatible now * switch /bin/sh over to eg dash (tbh I'm not sure what other alternative smallish shells exist) early *after* the next release and get people to test it. I'm afraid that there might be other applications that expect bash in /bin/sh. How does this sound? Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
On Wed, Aug 22, 2007 at 06:05:46PM +0200, Tilman Sauerbeck wrote:
treach [2007-08-22 17:39]:
Another, more debatable point is the use of a more standard adherent shell as the default, with the removal of bashisms from the rc scripts as an addon.
I've used dash quite successfully in the past for this, which is also used by debian/*buntu. It's a lot faster and smaller than bash, however, if used as /bin/sh it will trigger misbehaviour from broken software that assumes /bin/sh == /bin/bash. So far I've only heard of cdega having this issue though - I've come across nothing that complained so far myself (fwiw).
+1, I like the idea of removing bashisms from the RC scripts. Any objections? :p
No, as long as our scripts works with bash after that :-)
However, I'm not sure whether it's a good idea to start doing a /bin/sh switch now, ie shortly before release preparations begin.
However, we could: * make the scripts sh compatible now * switch /bin/sh over to eg dash (tbh I'm not sure what other alternative smallish shells exist) early *after* the next release and get people to test it. I'm afraid that there might be other applications that expect bash in /bin/sh.
I don't see any real benefit in switching /bin/sh to another shell, but potential problems, so my vote is a -1 here. regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
On Wed, Aug 22, 2007 at 05:39:46PM +0200, treach wrote:
On 16:07 Mon 20 Aug?, Juergen Daubert wrote:
On Fri, Aug 17, 2007 at 10:09:14PM +0200, Simone Rota wrote:
[...l]
Apart from the toolchain / kernel updates, I'd like to see some additional work for 2.4.
- UTF-8 X vote: 0
That's ok for me, but I don't see any improvement making it the default. Most people don't need it, and there are still some apps which are not UTF-8 ready, e.g. aterm or mc. Adding a wiki page how to switch to UTF-8 might be more helpful. And, of course, applications should be build with wide-charcater support if possible.
- Xorg 7.3 X vote: +1
- LiveCD X vote: +1
Finally, I think we'd benefit from setting an estimated release date / period, i.e. the beginning of october is my guess. ok
regards Juergen
#include <standard_Im_not_a_dev_disclaimer.h>
I'd like to see the addition/re-addition of some stuff in 2.4 that I feel would be very useful for various people.
In no particular order:
- gnuparted; for those who can't part with other, inferior operating systems, also handy in rescue situations.
- vwdial; Why did this get dropped of the iso? Apparently we still have some users relying on dial-up, or at least we had - until they tried upgrading to 2.3.
Mm.. Personally, I sometimes use dial-up (pppd), but never used vwdial. vwdial isn't mandatory for dial-uping.
- libdevmapper
Another, more debatable point is the use of a more standard adherent shell as the default
That means, if I'm bash user (and I guess most users use bash), starting with 2.x I'll have to keep two shells instead of just one. One for /bin/sh and another for interactive shell.
with the removal of bashisms from the rc scripts as an addon.
Nice.
I've used dash quite successfully in the past for this, which is also used by debian/*buntu.
As an interactive shell?
It's a lot faster and smaller than bash, however,
How faster is it in real life? Did you measure? Can you post boot times dash vs. bash? Or some another real life testcase. Good luck, -- Anton Vorontsov email: cbou@mail.ru backup email: ya-cbou@yandex.ru irc://irc.freenode.net/bd2
On Wed, Aug 22, 2007 at 10:04:51PM +0400, Anton Vorontsov wrote: [...]
Another, more debatable point is the use of a more standard adherent shell as the default
That means, if I'm bash user (and I guess most users use bash), starting with 2.x I'll have to keep two shells instead of just one. One for /bin/sh and another for interactive shell.
Oh, and for e.g. zsh users, that would mean that they have to keep _three_ shells. ;-) /bin/sh for posix-compliant scripts, /bin/bash for many-many scripts using bashism, and /bin/zsh for interactive shell. -- Anton Vorontsov email: cbou@mail.ru backup email: ya-cbou@yandex.ru irc://irc.freenode.net/bd2
On Wed, Aug 22, 2007 at 05:39:46PM +0200, treach wrote:
- vwdial; Why did this get dropped of the iso? Apparently we still have some users relying on dial-up, or at least we had - until they tried upgrading to 2.3.
wvdial and rp-pppoe were removed by mistake from the 2.3 iso and will be readded with 2.4 Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
El Mié 22 Ago 2007, treach escribió: [...]
Another, more debatable point is the use of a more standard adherent shell as the default, with the removal of bashisms from the rc scripts as an addon.
I've used dash quite successfully in the past for this, which is also used by debian/*buntu. It's a lot faster and smaller than bash, however, if used as /bin/sh it will trigger misbehaviour from broken software that assumes /bin/sh == /bin/bash. So far I've only heard of cdega having this issue though - I've come across nothing that complained so far myself (fwiw).
My vote is on removing bashisms from rc scripts, and to use #!/bin/bash in scripts that REQUIRE bash (eg: ldd). That way, if the user wants to replace /bin/sh with something else than bash, it will work right away. I couldn't care less if the default is to make /bin/sh = /bin/bash or any other shell that superseeds sh, after all, this is CRUX and people will change it to whatever they like best. I in particular change it to mksh. -- Alan
On Fri, 17 Aug 2007 19:26:29 +0200 Juergen Daubert <jue@jue.li> wrote:
- glibc 2.6.1 with kernel headers 2.6.22
Hi, I'd suggest to wait for Kernel 2.6.23. I can only speak for myself right now but I had problems with 2.6.22 when I tried it, and I use 2.6.23-rc2 right now which works pretty fine. Everything else sounds pretty good for me :) Cheers, Tim
Juergen Daubert [2007-08-17 19:26]:
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one.
Somewhat related: I'd like to build xorg/xorg-server without Xprint support starting with the next CRUX release. Reasons: it sucks, virtually nobody uses it, it's buggy and broken. For the majority of CRUX users this shouldn't be a problem, for the few (insane) others, I might create a port that enables it. Should you have objections to this, please let me know. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Tilman Sauerbeck schrieb:
Juergen Daubert [2007-08-17 19:26]:
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one.
Somewhat related: I'd like to build xorg/xorg-server without Xprint support starting with the next CRUX release.
Reasons: it sucks, virtually nobody uses it, it's buggy and broken.
ACK!
For the majority of CRUX users this shouldn't be a problem, for the few (insane) others, I might create a port that enables it.
I'd prefer a really minimal X installation (small "dependency footprint") and don't mind recompiling stuff to get dependencies resolved afterwards. Regards, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
On Fri, Aug 17, 2007 at 07:26:29PM +0200, Juergen Daubert wrote:
Hello CRUX maintainers,
Hello again,
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain.
To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now:
- gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22
- binutils 2.18.50
By mistake I took a cvs-snapshot version of binutils, not what we want for our new release? Apologize for that. The official release is still 2.17, but there is a newer one available at kernel.org [3], it's a 2.17+cvs and additional patches maintained by some RedHat people. Unfortunately they have removed all docs, generated with texinfo, from the tarball, so texinfo is a build-time dependency. A patch might be possible, but not a trivial one, if we want the man-pages. And, more important, I got a configure error from glibc with that version of binutils. I'd tend to stick with the official 2.17, updated binaries are available at [2]. Opinions ? best regards Juergen [2] http://crux.nu/~jue/tmp/ [3] http://gcc.gnu.org/ml/gcc/2007-08/msg00017.html -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Hello, Juergen! Juergen Daubert schrieb:
On Fri, Aug 17, 2007 at 07:26:29PM +0200, Juergen Daubert wrote:
Hello CRUX maintainers,
Hello again,
our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain.
To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now:
- gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22
- binutils 2.18.50
By mistake I took a cvs-snapshot version of binutils, not what we want for our new release? Apologize for that. [...] Opinions ?
Binutils 2.18 will be out very soon (like today, 27th August): http://www.cygwin.com/ml/binutils/2007-08/msg00085.html Regards, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
On Mon, Aug 27, 2007 at 05:56:37PM +0200, Clemens Koller wrote:
Hello, Juergen!
Hi Clemens,
Juergen Daubert schrieb:
On Fri, Aug 17, 2007 at 07:26:29PM +0200, Juergen Daubert wrote:
Hello CRUX maintainers, Hello again, our last CRUX release is nearly a half year ago, so I thought it might be a good idea to think about a new one. Moreover, there are new major releases of all parts of our standard toolchain.
To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now:
- gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22 - binutils 2.18.50 By mistake I took a cvs-snapshot version of binutils, not what we want for our new release? Apologize for that. [...] Opinions ?
Binutils 2.18 will be out very soon (like today, 27th August): http://www.cygwin.com/ml/binutils/2007-08/msg00085.html
many thanks for the hint! I suppose it's out of question that we will use binutils 2.18 now, I've uploaded new bootstrapped binaries of binutils, gcc and glibc to http://crux.nu/~jue/tmp/ Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Juergen Daubert [2007-08-17 19:26]:
- gcc 4.2.1
I'm not sure on this one. The list of "serious regression" bugs for 4.2.1 contains stuff like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32544 which makes me wonder how stable gcc 4.2.1 really is :/ Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Tilman Sauerbeck schrieb:
Juergen Daubert [2007-08-17 19:26]:
- gcc 4.2.1
I'm not sure on this one. The list of "serious regression" bugs for 4.2.1 contains stuff like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32544 which makes me wonder how stable gcc 4.2.1 really is :/
I'm using gcc-4.2.1 right now and didn't run into any severe problems. There was some discussion that gcc-4.2.1 will become gcc-4.3.3 or get some other strange number due to the GPLv3 relicensing. http://gcc.gnu.org/develop.html#timeline Regards, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19
Clemens Koller [2007-08-29 00:17]:
Tilman Sauerbeck schrieb:
Juergen Daubert [2007-08-17 19:26]:
- gcc 4.2.1
I'm not sure on this one. The list of "serious regression" bugs for 4.2.1 contains stuff like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32544 which makes me wonder how stable gcc 4.2.1 really is :/
I'm using gcc-4.2.1 right now and didn't run into any severe problems.
There was some discussion that gcc-4.2.1 will become gcc-4.3.3 or get some other strange number due to the GPLv3 relicensing.
Ah, I guess you meant gcc-4.2.2 and not 4.2.1, right? http://gcc.gnu.org/ml/gcc/2007-07/msg00389.html Their roadmap is a bit confusing atm, I have no clue whether waiting for 4.3.3 might be an option (though I didn't look too hard yet :P). Thanks for the heads-up on the binutils release, btw. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
On Tue, Aug 28, 2007 at 08:18:29PM +0200, Tilman Sauerbeck wrote:
Juergen Daubert [2007-08-17 19:26]:
- gcc 4.2.1
I'm not sure on this one. The list of "serious regression" bugs for 4.2.1 contains stuff like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32544 which makes me wonder how stable gcc 4.2.1 really is :/
That's true, but is 4.1.x really an option for 4.2? Anyway we have to decide which compiler we will use, or the release will certainly be delayed. BTW, there is an updated status report: http://gcc.gnu.org/ml/gcc/2007-09/msg00046.html I'd suggest to use 4.2.1 for our tests now and update to 4.2.2 as soon as available, so 4.2.2 will be the version on the 2.4 ISO. Regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Juergen Daubert [2007-09-09 18:54]:
On Tue, Aug 28, 2007 at 08:18:29PM +0200, Tilman Sauerbeck wrote:
Juergen Daubert [2007-08-17 19:26]:
- gcc 4.2.1
I'm not sure on this one. The list of "serious regression" bugs for 4.2.1 contains stuff like http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32544 which makes me wonder how stable gcc 4.2.1 really is :/
That's true, but is 4.1.x really an option for 4.2? Anyway we have to decide which compiler we will use, or the release will certainly be delayed.
BTW, there is an updated status report: http://gcc.gnu.org/ml/gcc/2007-09/msg00046.html
I'd suggest to use 4.2.1 for our tests now and update to 4.2.2 as soon as available, so 4.2.2 will be the version on the 2.4 ISO.
Alright, let's do it like that. Can you do the port upgrade please? Thanks, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Juergen Daubert [2007-08-17 19:26]:
To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now:
- gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22 - binutils 2.18.50
I've branched core.git off for 2.4: http://crux.nu/gitweb/?p=ports/core.git;a=shortlog;h=2.4 so far it only has the new glibc. Juergen, do you mind bumping binutils, gzip and perl in there? Otherwise I'll do it. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
On Wed, Aug 29, 2007 at 06:14:33PM +0200, Tilman Sauerbeck wrote:
Juergen Daubert [2007-08-17 19:26]:
To initiate the whole thing I've created updated ports of those stuff, all of them available from my private httpup-repo [1] for now:
- gcc 4.2.1 - glibc 2.6.1 with kernel headers 2.6.22 - binutils 2.18.50
I've branched core.git off for 2.4: http://crux.nu/gitweb/?p=ports/core.git;a=shortlog;h=2.4
Great, thanks Tilman.
so far it only has the new glibc.
Juergen, do you mind bumping binutils, gzip and perl in there?
Will do it tomorrow morning. Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
participants (10)
-
Alan Mizrahi -
Anton Vorontsov -
Clemens Koller -
Juergen Daubert -
Matt Housh -
Simon Gloßner -
Simone Rota -
Tilman Sauerbeck -
Tim Biermann -
treach