Project

General

Profile

prelude-client-argv.patch

untested patch! - , 06/29/2007 05:34 PM

Download (5.56 KB)

View differences:

src/prelude-client.c (copie de travail)
1106 1106 
        int ret;
1107 1107 
        prelude_string_t *err;
1108 1108 
        prelude_option_warning_t old_warnings;
1109 
        char *program;
1109 1110 

  		




  1110
  1111
  
    
        prelude_return_val_if_fail(client, -1);

  		




  1111
  1112
  
    

  		




  ......




  1123
  1124
  
    
        if ( ret < 0 )

  		




  1124
  1125
  
    
                return handle_client_error(client, ret);

  		




  1125
  1126
  
    

  		




  1126
  
  
    
        ret = fill_client_infos(client, _prelude_internal_argv[0]);

  		




  
  1127
  
    
        if (0 < _prelude_internal_argc)

  		




  
  1128
  
    
                program = _prelude_internal_argv[0];

  		




  
  1129
  
    
        else

  		




  
  1130
  
    
                program = NULL;

  		




  
  1131
  
    
        ret = fill_client_infos(client, program);

  		




  1127
  1132
  
    
        if ( ret < 0 )

  		




  1128
  1133
  
    
                return handle_client_error(client, ret);

  		




  1129
  1134
  
    

  		












  

    
      INSTALL	(copie de travail)
    
  





  1
  1
  
    
Installation Instructions

  		




  2
  2
  
    
*************************

  		




  3
  3
  
    

  		




  4
  
  
    
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free

  		




  5
  
  
    
Software Foundation, Inc.

  		




  
  4
  
    
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,

  		




  
  5
  
    
2006 Free Software Foundation, Inc.

  		




  6
  6
  
    

  		




  7
  7
  
    
This file is free documentation; the Free Software Foundation gives

  		




  8
  8
  
    
unlimited permission to copy, distribute and modify it.

  		




  ......




  10
  10
  
    
Basic Installation

  		




  11
  11
  
    
==================

  		




  12
  12
  
    

  		




  13
  
  
    
These are generic installation instructions.

  		




  
  13
  
    
Briefly, the shell commands `./configure; make; make install' should

  		




  
  14
  
    
configure, build, and install this package.  The following

  		




  
  15
  
    
more-detailed instructions are generic; see the `README' file for

  		




  
  16
  
    
instructions specific to this package.

  		




  14
  17
  
    

  		




  15
  18
  
    
   The `configure' shell script attempts to guess correct values for

  		




  16
  19
  
    
various system-dependent variables used during compilation.  It uses

  		




  ......




  23
  26
  
    

  		




  24
  27
  
    
   It can also use an optional file (typically called `config.cache'

  		




  25
  28
  
    
and enabled with `--cache-file=config.cache' or simply `-C') that saves

  		




  26
  
  
    
the results of its tests to speed up reconfiguring.  (Caching is

  		




  
  29
  
    
the results of its tests to speed up reconfiguring.  Caching is

  		




  27
  30
  
    
disabled by default to prevent problems with accidental use of stale

  		




  28
  
  
    
cache files.)

  		




  
  31
  
    
cache files.

  		




  29
  32
  
    

  		




  30
  33
  
    
   If you need to do unusual things to compile the package, please try

  		




  31
  34
  
    
to figure out how `configure' could check whether to do them, and mail

  		




  ......




  35
  38
  
    
may remove or edit it.

  		




  36
  39
  
    

  		




  37
  40
  
    
   The file `configure.ac' (or `configure.in') is used to create

  		




  38
  
  
    
`configure' by a program called `autoconf'.  You only need

  		




  39
  
  
    
`configure.ac' if you want to change it or regenerate `configure' using

  		




  40
  
  
    
a newer version of `autoconf'.

  		




  
  41
  
    
`configure' by a program called `autoconf'.  You need `configure.ac' if

  		




  
  42
  
    
you want to change it or regenerate `configure' using a newer version

  		




  
  43
  
    
of `autoconf'.

  		




  41
  44
  
    

  		




  42
  45
  
    
The simplest way to compile this package is:

  		




  43
  46
  
    

  		




  44
  47
  
    
  1. `cd' to the directory containing the package's source code and type

  		




  45
  
  
    
     `./configure' to configure the package for your system.  If you're

  		




  46
  
  
    
     using `csh' on an old version of System V, you might need to type

  		




  47
  
  
    
     `sh ./configure' instead to prevent `csh' from trying to execute

  		




  48
  
  
    
     `configure' itself.

  		




  
  48
  
    
     `./configure' to configure the package for your system.

  		




  49
  49
  
    

  		




  50
  
  
    
     Running `configure' takes awhile.  While running, it prints some

  		




  51
  
  
    
     messages telling which features it is checking for.

  		




  
  50
  
    
     Running `configure' might take a while.  While running, it prints

  		




  
  51
  
    
     some messages telling which features it is checking for.

  		




  52
  52
  
    

  		




  53
  53
  
    
  2. Type `make' to compile the package.

  		




  54
  54
  
    

  		




  ......




  78
  78
  
    
by setting variables in the command line or in the environment.  Here

  		




  79
  79
  
    
is an example:

  		




  80
  80
  
    

  		




  81
  
  
    
     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

  		




  
  81
  
    
     ./configure CC=c99 CFLAGS=-g LIBS=-lposix

  		




  82
  82
  
    

  		




  83
  83
  
    
   *Note Defining Variables::, for more details.

  		




  84
  84
  
    

  		




  ......




  87
  87
  
    

  		




  88
  88
  
    
You can compile the package for more than one kind of computer at the

  		




  89
  89
  
    
same time, by placing the object files for each architecture in their

  		




  90
  
  
    
own directory.  To do this, you must use a version of `make' that

  		




  91
  
  
    
supports the `VPATH' variable, such as GNU `make'.  `cd' to the

  		




  
  90
  
    
own directory.  To do this, you can use GNU `make'.  `cd' to the

  		




  92
  91
  
    
directory where you want the object files and executables to go and run

  		




  93
  92
  
    
the `configure' script.  `configure' automatically checks for the

  		




  94
  93
  
    
source code in the directory that `configure' is in and in `..'.

  		




  95
  94
  
    

  		




  96
  
  
    
   If you have to use a `make' that does not support the `VPATH'

  		




  97
  
  
    
variable, you have to compile the package for one architecture at a

  		




  98
  
  
    
time in the source code directory.  After you have installed the

  		




  99
  
  
    
package for one architecture, use `make distclean' before reconfiguring

  		




  100
  
  
    
for another architecture.

  		




  
  95
  
    
   With a non-GNU `make', it is safer to compile the package for one

  		




  
  96
  
    
architecture at a time in the source code directory.  After you have

  		




  
  97
  
    
installed the package for one architecture, use `make distclean' before

  		




  
  98
  
    
reconfiguring for another architecture.

  		




  101
  99
  
    

  		




  102
  100
  
    
Installation Names

  		




  103
  101
  
    
==================

  		




  ......




  190
  188
  
    
     ./configure CC=/usr/local2/bin/gcc

  		




  191
  189
  
    

  		




  192
  190
  
    
causes the specified `gcc' to be used as the C compiler (unless it is

  		




  193
  
  
    
overridden in the site shell script).  Here is a another example:

  		




  
  191
  
    
overridden in the site shell script).

  		




  194
  192
  
    

  		




  195
  
  
    
     /bin/bash ./configure CONFIG_SHELL=/bin/bash

  		




  
  193
  
    
Unfortunately, this technique does not work for `CONFIG_SHELL' due to

  		




  
  194
  
    
an Autoconf bug.  Until the bug is fixed you can use this workaround:

  		




  196
  195
  
    

  		




  197
  
  
    
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent

  		




  198
  
  
    
configuration-related scripts to be executed by `/bin/bash'.

  		




  
  196
  
    
     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash

  		




  199
  197
  
    

  		




  200
  198
  
    
`configure' Invocation

  		




  201
  199
  
    
======================