[haiku-commits] Re: Terminal broken

  • From: Stephan Assmus <superstippi@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 17 Aug 2010 15:56:43 +0200

Am 17.08.2010 15:50, schrieb pulkomandy:
On Tue, Aug 17, 2010 at 03:41:44PM +0200, Stephan Assmus wrote:
Am 17.08.2010 13:42, schrieb pulkomandy:
Sorry for jumping to conclusions so quickly. My image is also a
clean build, but I will retest after jam clean. It just seemed very
likely to me that the breakage was caused by your changes.

I don't say it isn't related, but I did test my changes before
commiting. Some things that could have worked before but would now break
would be :
  * bash executable working ok, but /bin/sh (now used by terminal) is wrong
  * user profile selecting another shell that doesn't work
  * bash behaving as a posix shell because it is started as /bin/sh, and
not liking something in /etc/profile because of that

But by testing your changes, I mean to test with a default install.
I have no local changes in my source tree at the moment, and I have
no configuration changes regarding profile or /bin/sh or anything
related to the Terminal except for the default window size. So by
testing a *default* image, you should see the same broken behaviour
that I am seeing. (My new build finished, so I can check now if I
had somehow a broken build... will report shortly.)

That's what I do (I did another build just to be sure), and I still
don't see a problem here. I tested it as much as I could, so I'm now
thinking the problem is either on your side, or me doing something
wrong somewhere. No idea how to fix it in both cases.

Rename your UserBuildConfig, do "svn status" over your entire tree to check if you have any uncommited changes, issue a jam -q haiku-image, or @alpha-raw or something and boot the image in qemu. Simply launch a Terminal, the problem is reproducable everytime. I am building a GCC4 based hybrid image, but I don't anticipate that building a GCC2 image will hide the error.

Best regards,
-Stephan


Other related posts: