Displaying 10 results from an estimated 10 matches for "set_directori".
Did you mean:
set_directory
2004 Sep 18
3
[LLVMdev] Files to lib/System/Win32
Here's my first take on Path.cpp. It has a few holes still but it ought
to be basically functional.
A few observations:
First, the Win32 version still has a lot of code in common with Unix.
This code should be pulled out into a common file.
Second, some of the functions leave me scratching me head. What purpose
does create_file serve? Is there really a need to create empty files?
(It
2004 Sep 17
0
[LLVMdev] Files to lib/System/Win32
Jeff,
Your patch has been committed.
Thanks!
Reid.
Jeff Cohen wrote:
> Alas, you missed a serious bug in that same function. Patch attached to
> fix it and improve some comments. No more late night coding for me :)
>
> That leaves Path.cpp. Once that's done I can actually try and execute
> this stuff.
>
>
> On Thu, 16 Sep 2004 08:55:28 -0700
> Reid Spencer
2004 Sep 17
2
[LLVMdev] Files to lib/System/Win32
Alas, you missed a serious bug in that same function. Patch attached to
fix it and improve some comments. No more late night coding for me :)
That leaves Path.cpp. Once that's done I can actually try and execute
this stuff.
On Thu, 16 Sep 2004 08:55:28 -0700
Reid Spencer <reid at x10sys.com> wrote:
> This version has been committed to CVS with one minor change:
> I made the
2004 Sep 18
0
[LLVMdev] Files to lib/System/Win32
Patch looks good so I committed it. I'd be interested in knowing what
your test results are once you start testing with the Win32 port.
Reid.
On Sat, 2004-09-18 at 12:01, Jeff Cohen wrote:
> Here's my first take on Path.cpp. It has a few holes still but it ought
> to be basically functional.
>
> A few observations:
>
> First, the Win32 version still has a lot of code
2004 Sep 01
0
[LLVMdev] FreeBSD Support In lib/System
Jeff & others
A couple words on how lib/System works that might help you.
1. The configure script identifies the build host and puts it in the
$build variable. We use that to determine the basic kind of
platform
and put it in a variable named $OS. The value of $OS can be: Linux,
FreeBSD, Interix, SunOS, Darwin, etc.
2. The platform name is used to create a link from
2004 Aug 31
9
[LLVMdev] POSIX compliance
Reid,
>As for Interix support in general, I'm having a hard time determining
>which variant of Unix Interix implements. It seems to be partially Posix
>1 and partially Posix 2 based. Do you have any further information
>related to the specific standards supported by Interix? I don't want to
>incorrectly categorize the Interix support.
I've discussed this subject with
2004 Aug 31
0
[LLVMdev] FreeBSD Support In lib/System
Jeff/Vladimir:
As with Interix, I've recently added support for FreeBSD into
lib/System. Currently, the implementation of FreeBSD just uses the
"generic Unix" implementation which probably should work on FreeBSD. If
not, I would appreciate it if you could make patches in the FreeBSD
directory. If you do, don't forget that you need to remove anything that
doesn't work in the
2007 Mar 28
0
[925] branches/wxruby2/wxwidgets_282/doc/textile/filedialog.txtl: Improvements to doc from wxWidgets 2.8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2007 Apr 12
9
taille de caractère
en fait je vous renvoi ce message car maintenant la taille de la police change au bout de 500 lignes environ, alors que j''avais reussi à garder la taille jusqu''à environ 5000 lignes.
Je ne comprend pas. Est-ce que c''est instable?
le bout de code que vous m''avez envoyer ne marche pas.
merci
Sebastien
_______________________________________________
wxruby-users
2008 May 05
11
puppetmasterd --mkusers
I''m trying to run puppetmasterd the first time with --mkusers. It
fails with the following error message:
001 # /usr/bin/puppetmasterd --mkusers
Could not configure for running; got 1 failure(s)
Adding --verbose and --debug does nothing to improve the output. How
do I begin to debug this?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are