headers
Les Harris | 10 Jan 2008 02:27
Picon

Gnome-Terminal Not Starting

Bizarre problem here.  Any gnome app is refusing to launch. No error
message, no seg fault, just returns immediately to console.

X works fine and I can launch gtk+-only apps like Gvim just fine.

GDB is showing the following when I try to launch gnome-terminal:

gdb: unknown target exception 0xc0000139 at 0x7c964ed1

Program received signal ?, Unknown signal.

Program exited with code 030000000471.

Anyone have any ideas?

Thanks!

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
Permalink | Reply | 1 comment |
headers
Yaakov (Cygwin Ports | 11 Jan 2008 05:55
Picon
Gravatar

Re: Gnome-Terminal Not Starting


Les Harris wrote:
| Bizarre problem here.  Any gnome app is refusing to launch. No error
| message, no seg fault, just returns immediately to console.
|
| X works fine and I can launch gtk+-only apps like Gvim just fine.

Yes, I can confirm that, but AFAICS it's really VTE; you'll notice that
/usr/bin/vte doesn't work either.  It's been bugging me since the GNOME
2.20.2 upgrade, as I was using gnome-terminal regularly until then.

I now suspect that this was caused by a bug in glib-2.14 which was fixed
in 2.14.5; I just built and installed the latter and both vte and
gnome-terminal run now.

So please sit tight until the next upload, which I will try to do soon,
and let me know what the result is after upgrading.

Thanks for the report.

Yaakov
Cygwin Ports
Permalink | Reply | 0 comments |
headers
Yaakov (Cygwin Ports | 11 Jan 2008 06:29
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)


Reini Urban wrote:
| Are you planning recompiling the perl-* modules as perl-5.10 test
| versions for an easier switch?

Reini, if I may ask:

1) how far away is 5.10.1?

2) is it too late to change the last component
archlib/vendorarch/sitearch to something slightly more descriptive then
"cygwin"?  The problem is that due to caps insensitivity, e.g.
{vendorlib}/Cygwin/Version.pm (from upset) and {vendorarch}/version.pm
(from perl-version, now part of the core) are the same except for
capitalization, which leads to horrible problems using version or
Cygwin::Version.

While I fixed this in my local copy of upset to Cygwin::Setup::Version,
there is still potential problems with such a simple name.  I realize
that archname is quite long, but perhaps there is a compromise in the
middle which avoids this problem?

Yaakov
Cygwin Ports
Permalink | Reply | 9 comments |
headers
Reini Urban | 11 Jan 2008 12:18
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)

2008/1/11, Yaakov (Cygwin Ports) <yselkowitz@...>:
> Reini Urban wrote:
> | Are you planning recompiling the perl-* modules as perl-5.10 test
> | versions for an easier switch?
>
> Reini, if I may ask:
>
> 1) how far away is 5.10.1?

That Q should go to Rafael. It dont believe so early.
Just one performance bug was found so far (copying  <at> _),
and I put this into my new interim -3 package.

But it is still in test and I can change it.

> 2) is it too late to change the last component
> archlib/vendorarch/sitearch to something slightly more descriptive then
> "cygwin"?  The problem is that due to caps insensitivity, e.g.
> {vendorlib}/Cygwin/Version.pm (from upset) and {vendorarch}/version.pm
> (from perl-version, now part of the core) are the same except for
> capitalization, which leads to horrible problems using version or
> Cygwin::Version.
>
> While I fixed this in my local copy of upset to Cygwin::Setup::Version,
> there is still potential problems with such a simple name.  I realize
> that archname is quite long, but perhaps there is a compromise in the
> middle which avoids this problem?

Hmm. Good argument.
Maybe a -i386 suffix against the -i64 suffix is in order.
(Continue reading)

Permalink | Reply | 8 comments |
headers
Yaakov (Cygwin Ports | 11 Jan 2008 13:56
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)


Reini Urban wrote:
| Hmm. Good argument.
| Maybe a -i386 suffix against the -i64 suffix is in order.
| i64 assumes fastcall-like calling conventions which don't support.
| (first 4 args via registers, rest on the stack)
|
| And later we want to come up with a proper CPAN release of a Cygwin
package.
| We want more API functions from the dll, and mount table handling.
| Cygwin::Version as package is still forbidden. hmm.

The change would mean, of course, rebuilding the other modules which
you've already done once for 5.10, but as this is still in experimental,
the end users shouldn't really be affected yet.

If you're prepared to make this change, I would propose the following
schedule:

* I wrap up my current dev cycle and upload over the weekend, which
would be a "pre-5.10" snapshot;

* you re-release 5.10 with the expanded archlib ASAP;

* I then begin reviewing all 120+ Perl modules and anything else
depending on (lib)perl for 5.10, eliminating any cruft, duplication,
etc. and rebuilding the rest (could easily take 2+ weeks of continued
development);

* once complete, we coordinate your stabilization of 5.10 in the distro
(Continue reading)

Permalink | Reply | 6 comments |
headers
Yaakov (Cygwin Ports | 11 Jan 2008 14:00
Picon
Gravatar

Re: upset and Cygwin::Setup


Reini Urban wrote:
| Maybe release the Cygwin::Setup package on CPAN?
| I fixed the same also in my local copy of upset. => Cygwin::Setup

I have sometimes considered doing just that.  I doubt cgf would be
pleased about such a release, but "hiding" upset has left legitimate
3PPers like me in a difficult position.

I've seen some of your changes; perhaps we could work together to merge
our forks.  A performance enhancement is also desperately needed, as I
see every time with my huge repo.

But how is upset/Cygwin::Setup licensed?  I don't see any information in
my files, which IIRC haven't been changed in that respect.

Yaakov
Cygwin Ports
Permalink | Reply | 0 comments |
headers
bob davis | 12 Jan 2008 02:17
Gravatar

install order

Hi I installed with setup from:
http://sources-redhat.mirror.redwire.net/cygwin
which is a cygwin mirror site.
But I really needed gftp and found it on your site.
So added your setup url:
ftp://sunsite.dk/projects/cygwinports
and installed gftp and it worked.

My only question is that if I go back to the cygwin mirror site it wants 
to downgrade a bunch of packages. Is there a sequence or setting so that 
I can run setup for both sites at the same time and have it do the right 
thing?

Also (ok so there were 2 questions) I had some trouble at first because 
I first installed from:
http://cygnome.sourceforge.net/
and found it was out of date and not working.
I then found your site and updated from it but I got a messed up mixture 
of packages and nothing worked.
So whats the correct packages/procedure to uninstall stuff so I can 
install the correct gnome packages. I really didn't want to uninstall 
all of cygwin and then reinstall.

thanks
bob

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Reini Urban | 12 Jan 2008 16:27
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)

2008/1/11, Yaakov (Cygwin Ports) <yselkowitz@...>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Reini Urban wrote:
> | Hmm. Good argument.
> | Maybe a -i386 suffix against the -i64 suffix is in order.
> | i64 assumes fastcall-like calling conventions which don't support.
> | (first 4 args via registers, rest on the stack)
> |
> | And later we want to come up with a proper CPAN release of a Cygwin
> package.
> | We want more API functions from the dll, and mount table handling.
> | Cygwin::Version as package is still forbidden. hmm.
>
> The change would mean, of course, rebuilding the other modules which
> you've already done once for 5.10, but as this is still in experimental,
> the end users shouldn't really be affected yet.
>
> If you're prepared to make this change, I would propose the following
> schedule:
>
> * I wrap up my current dev cycle and upload over the weekend, which
> would be a "pre-5.10" snapshot;
>
> * you re-release 5.10 with the expanded archlib ASAP;

not over this weekend please!
I'm still on a business trip somewhere in detroit with only my laptop
and poor internet connection.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Yaakov (Cygwin Ports | 13 Jan 2008 03:53
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)


Reini Urban wrote:
| not over this weekend please!
| I'm still on a business trip somewhere in detroit with only my laptop
| and poor internet connection.
| next weekend would be better.

That's fine, it can happen whenever you're ready.  I'm holding off on
almost anything perl-related until then.

| most modules build out of the box.

Most??  Which don't?

| and the errors I found are for 5.8.8 also. just the B modules are
| problematic, B::Generate I fixed recently.
| The 5.10 B compiler suite is not ready yet.

Does that affect the general readability of 5.10 for general
consumption?  I'm a bit concerned about making such a major upgrade too
early.

| name proposals of the archlib? The generated ones as they used to be
| in older days?

AFAIK our perl packages used to use the default, which is archname:
cygwin-thread-multi-64int.  It's a bit long, and makes for file listings
more than 80 chars wide.  Some ideas from what other distros *would* do,
based on their other platforms:
* Fedora, Gentoo: i686-cygwin-thread-multi
(Continue reading)

Permalink | Reply | 2 comments |
headers
Reini Urban | 13 Jan 2008 16:57
Picon
Gravatar

Re: perl 5.10 (was [Cygwin-ports-announce] Uploads: 2007-Dec-26)

2008/1/12, Yaakov (Cygwin Ports) <yselkowitz@...>:
> Reini Urban wrote:
> | not over this weekend please!
> | I'm still on a business trip somewhere in detroit with only my laptop
> | and poor internet connection.
> | next weekend would be better.
>
> That's fine, it can happen whenever you're ready.  I'm holding off on
> almost anything perl-related until then.
>
> | most modules build out of the box.
>
> Most??  Which don't?

See http://cpantesters.perl.org/author/RURBAN.html
for 5.10 only

> | and the errors I found are for 5.8.8 also. just the B modules are
> | problematic, B::Generate I fixed recently.
> | The 5.10 B compiler suite is not ready yet.
>
> Does that affect the general readability of 5.10 for general
> consumption?  I'm a bit concerned about making such a major upgrade too
> early.

No, not all. The perl compiler was removed from CORE for all platforms,
and is a standalone CPAN module now, where certain parts don't work
yet good enough to produce e.g. optimized C code. Nobody stepped
in yet to complete it.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane