Hi cygwinners,
as you mentioned in the last months, i'd a lot of problems to fulfill my task
as cygwin emacs maintainer. This has many reasons. There is this rsync/cygport
problem mentioned sometimes before i have at my machine, but also a lack of
time for the cygwin work coming from a really s
Ken Brown schrieb:
> I'd like some advice as to how to proceed. Sharing the job with Steffen
> would seem to make the most sense, but I'm not sure exactly how that
> would work since he can't run cygport.
Hi Ken,
thanx for your offer. I'm in a hurry currently but i'll contact you by email
short
It might be clearer if 'xemacs-emacs-common' was renamed using the
plural for emacs, that is, 'emacsen-common'.
Good idea. But i can live with 'xemacs-emacs-common' too.
Also, I'm not sure that the package should have the same version
number ('21.5.28.3') as xemacs. That versioning
suggests th
Corinna Vinschen schrieb:
> can you do me a favor? Can you have a look into the FAQ entries "Is
> there a Cygwin port of GNU Emacs?" and the next one "What about NT
> Emacs?" and suggest a rewrite? The information given in these two FAQ
> entries is certainly outdated, but I'm not quite sure how t
Ken Brown schrieb:
> You received a reply on the main cygwin mailing list to your first
> message about this problem:
>
>http://cygwin.com/ml/cygwin/2008-10/msg00524.html
>
> By the way, do you subscribe to that list? There was quite a bit of
> emacs discussion in December.
Sorry, i didn't
The problem is still existing:
$ cygport emacs-22.3-1.cygport prep
Preparing emacs-22.3-1
*** Info: SOURCE 1 signature follows:
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Fri Sep 5 18:34:56 2008 WEST using DSA
Steffen Sledz wrote:
> Now that gcc4 is available in release-2 i wanted to make a new try in
> building emacs there, but i failed in the first step. :(
>
> $ cygport emacs-22.3-1.cygport prep
>>>> Preparing emacs-22.3-1
> *** Info: SOURCE 1 signature follows:
> gpg:
Now that gcc4 is available in release-2 i wanted to make a new try in building
emacs there, but i failed in the first step. :(
$ cygport emacs-22.3-1.cygport prep
Preparing emacs-22.3-1
*** Info: SOURCE 1 signature follows:
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.
Corinna Vinschen schrieb:
Please test and please create new packages for 1.7 as far as necessary.
Will release-2 come with gcc4? As you can remember i had big problems making a
gcc3 built emacs for cygwin.
Steffen
Corinna Vinschen schrieb:
> Please test and please create new packages for 1.7 as far as necessary.
Is there a chance, that 1.7 comes with gcc4? As you can remember i had
big problems to make a gcc3 built emacs for Cygwin.
Steffen
I tried to install setup-1.7 on a system running a "normal" release
before. I've deleted the whole C:\cygwin dir from the disk and removed
all cygwin/cygnus related items from the registry.
But after running the new setup the mounts for /usr/bin and /usr/lib
where missing. Also there is no /et
Hi Corinna,
yes, I'm still with you. :)
And Mark ist right with his message. I'd some dirty problems with gcc 3
compiled Emacs 22.1. :(
Mark Harig wrote:
Resolve problems that are preventing a Cygwin gcc 4 ->
Compile Emacs 22.1 with gcc 4 ->
Test to determine whether the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen Sledz schrieb:
> Eric Blake schrieb:
>> If you set SIG in your environment (to anything, although 'export SIG=1'
>> seems simplest), then cygport will automatically prompt for creation of,
>> and distribute, .s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> If you set SIG in your environment (to anything, although 'export SIG=1'
> seems simplest), then cygport will automatically prompt for creation of,
> and distribute, .sig files as part of the package phase...
OK, I'll try that.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cygport README mentioned GPG .sig files for all the files used to build
up a package. As I could see, the prep stage checks these. But they are
not made part to the final source package in package stage. Is this
intentionally or a bug?
Steffen
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> Go ahead and send a release announcement, so hopefully you can get
> some more testers willing to try the version while it is still
> experimental.
Is there a template for such announcements?
Steffen
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 19 Jul 2007, Steffen Sledz wrote:
> I hope all wishes - espacially from Eric - are fulfilled now. ;-)
Oh, sorry. I forgot something.
Eric, I'v not checked the problem with the space in the Windows user name.
But I'll do t
n/emacs-leim/emacs-leim-22.1-3.tar.bz2>
<http://www.zone42.org/cygwin/emacs-leim/emacs-leim-22.1-3-src.tar.bz2>
<http://www.zone42.org/cygwin/emacs-leim/setup.hint>
You can also install directly from:
<http://www.zone42.org/cygwin/setup.ini>
Steffen Sledz
-BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Jul 2007, Eric Blake wrote:
> > Another newbie question at this point: What's the right way to create
> > the postinstall script? Currently there is one generated by cygport
> > containing the install-info stuff.
>
> Simply create a file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> I'd still like to see a -3 that takes an alternatives-based approach. To
> do that, you need to add a dependency on alternatives, then in your
> postinstall script, do something like this (looking at
> /etc/postinstall/automake1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> I'd still like to see a -3 that takes an alternatives-based approach. To
> do that, you need to add a dependency on alternatives, then in your
> postinstall script, do something like this (looking at
> /etc/postinstall/automake1.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> Also, your .cygport package does the following:
>
> # build non-X11 binary first
> LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base'\
> cygconf --with-x=no
> cygmake LD='$(CC)'
> # save non-
cs-leim-22.1-2.tar.bz2>
<http://www.zone42.org/cygwin/emacs/emacs-leim/setup.hint>
You can also install directly from:
<http://www.zone42.org/cygwin/setup.ini>
Steffen Sledz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://eni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake schrieb:
> Why did the package grow from 8meg to 17meg? Not necessarily a problem,
> if there is a good reason for it, but it seems a bit odd.
The emacs.exe binary itself is about 15MB (stripped). ;-)
> Why did the package shrink from 4.5
Eric Blake schrieb:
> Currently, emacs and emacs-X11 both provide /usr/bin/emacs.exe. Which
> means whichever package is installed last wins. I would much rather that
> you used the 'alternatives' package, and instead of directly providing
> /usr/bin/emacs.exe, instead provide two differently-nam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 10 Jul 2007, Corinna Vinschen wrote:
> > > xemacs-emacs-common:(used to conflict with emacs-21.2 now with
> > > upcoming emacs-22.1)
> > > /usr/bin/b2m.exe
> > > /usr/bin/rcs-checkin
> >
> > No idea.
>
> That's one between Volker and
On Tue, 10 Jul 2007, Dr. Volker Zell wrote:
> I splitted out the following conflicting files from my xemacs package:
What's the right way to handle such conflicts?
>
> xemacs-tags:(conflicts with ctags-5.6 and now with upcoming
> emacs-22.1)
> usr/bin/ctags.exe
> usr/bin/etags.e
On Mon, 9 Jul 2007, Eric Blake wrote:
> I will be trying them out this week.
Thx
> But first, a suggestion.
> Currently, emacs and emacs-X11 both provide /usr/bin/emacs.exe. Which
> means whichever package is installed last wins
If I made it right they don't. Package emacs provides
/usr/b
is obsolete as an own package. This is an empty package moving
emacs-leim to _obsolete:
<http://www.zone42.org/cygwin/emacs/emacs-leim/emacs-leim-22.1-1.tar.bz2>
<http://www.zone42.org/cygwin/emacs/emacs-leim/setup.hint>
You can also install directly from:
<http://www.zone42.org/
Brian Dessent schrieb:
>> 3. Same question for the build requirements.
>
> There's no automatic way to determine this, you just have to know which
> developer tools are required to build the software. For the most part it's
> pretty straightforward, e.g. it requires the 'make' package if a step w
My work at the new emacs packages makes good progress. The cygport stuff
is really comfortable. I hope, that I can present a new version in the
next days for testing.
But also after reading all the documentation there are some last
questions (if I've overlooked something please forgive me):
1. Wh
uot; | tr
-s " " " " | cut -f 1`)
I'm not familiar with cygwin development. What's the right way to report
such patches? How can i find and contact the maintainer of this package?
Regards,
Steffen Sledz
32 matches
Mail list logo
