delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Sun, 10 Jun 2001 16:34:55 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: confstr v2 |
Message-ID: | <3B23A1AF.185.136FE1@localhost> |
In-reply-to: | <9003-Sun10Jun2001200407+0300-eliz@is.elta.co.il> |
References: | <200106101441 DOT KAA11909 AT envy DOT delorie DOT com> (message from DJ Delorie on Sun, 10 Jun 2001 10:41:56 -0400) |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> > True, but in our case it depends on nothing *but* environment > > variables, so what can we do? I agree. The POSIX docs are assuming an environment where the placement of system files, etc. is almost hard-coded. Ours is not. > If so, how about if the > original value of DJDIR is not stashed away by the startup code unless > confstr is linked in? A function in confstr.c with the constructor attribute would work. Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |