zsh-workers
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: 'whence' question and others
Date: Sun, 09 Nov 2014 21:15:05 -0800	[thread overview]
Message-ID: <546049D9.4030806@eastlink.ca> (raw)
In-Reply-To: <141109105139.ZM27532@torch.brasslantern.com>

On 11/09/2014 10:51 AM, Bart Schaefer wrote:

Gentlemen,

A few questions before I start applying patches:

Does it matter if we 'make' from the Src directory vs. from it's parent?
It seems to work either way.

How often does one have to './configure'?

Rebuilding from virgin source, I ended up with a different size for zsh,
that's a bit scary, is it ok, or did I manage to farkle something? The 
new sized
build has been running without obvious trouble for several days.

Original:
-rwxr-xr-x 1  708980 2014-10-22//19:16:30 Src/Virgin/zsh*
Used for several days:
-rwxr-xr-x 1 711892 2014-11-04//19:59:26 
/usr/local/bin/zsh-test2-orig-rebuild*
Rebuilt just now:
-rwxr-xr-x 1  711860 2014-11-09//21:00:54 Src/zsh*


Where does one find function help in gcc?  I'm still using my ancient 
Borland C
manuals.

I managed to create a bit of a disaster with my 'printf()s' used for 
tracing, several
system files were trashed, which isn't exactly surprising, since so many 
files
can be open.  Would "fprintf(stderr, ..." be any safer?  What's the 
standard way of
doing that sort of thing?  I still think like a DOS man.

    utils.c:(.text+0x344e): warning: the use of `mktemp' is dangerous, 
better use `mkstemp' or `mkdtemp'

Anything to learn from the warning?  Can it be got rid of?


  reply	other threads:[~2014-11-10  4:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <545A6D66.3080500@eastlink.ca>
     [not found] ` <1458.1415209763@thecus.kiddle.eu>
     [not found]   ` <20141105180035.22f6e9b1@pwslap01u.europe.root.pri>
     [not found]     ` <141105204330.ZM2973@torch.brasslantern.com>
2014-11-06 21:10       ` 'whence' question Peter Stephenson
2014-11-06 21:58         ` Bart Schaefer
2014-11-08 20:41           ` Peter Stephenson
2014-11-09 18:51             ` Bart Schaefer
2014-11-10  5:15               ` Ray Andrews [this message]
2014-11-10  8:20                 ` 'whence' question and others Bart Schaefer
2014-11-10  8:23                   ` Bart Schaefer
2014-11-10 16:57                   ` Ray Andrews
2014-11-10 19:53                     ` Vin Shelton
2014-11-11 16:52               ` 'whence' question Ray Andrews
2014-11-11 19:14                 ` Bart Schaefer
2014-11-11 19:38                   ` Bart Schaefer
2014-11-11 20:22                   ` Ray Andrews
2014-11-11 18:16               ` Ray Andrews
2014-11-11 19:33                 ` Bart Schaefer
2014-11-11 20:40                   ` Ray Andrews
2014-11-08 21:55           ` Bart Schaefer
2014-11-10 10:04             ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=546049D9.4030806@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).