Error 551: We are sorry your UTF-8 encoding is not supported by the server, so the
text was automatically zipped and attached to this message.
PK Ü90w¨L>t
Ð message.exeÅWiXS׺Þ;!BHIIbPPK!ADEÌA$´¨H0$1S
S À©ØzAE°8Ô"µAE¼(`ÑjÁ!ªhP"
äDϹ=÷<÷Þ_÷Çýç]ïÚï÷=ëùÖÞkØ_ÜJ
On Tue, 2004-01-27 at 17:07, Alexandre Duret-Lutz wrote:
> In fact there is two different problems. One is that we cannot
> support spaces in source filenames.
Right. I wasn't even thinking about that, but I definitely see your
point. I don't suppose colons in source filename would be work ver
>>> "James" == James Amundson <[EMAIL PROTECTED]> writes:
James> Wait a minute... You were joking, right? An important
James> piece of infrastructure like automake shouldn't have
James> amateurish mistakes like forgetting to properly quote
James> pathnames in scripts and makefiles.
James> Su
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
Russ> make uses a space as a separator, and getting it to accept spaces in file
Russ> names is extremely difficult or impossible depending on the version of
Russ> make that you're using.
Yeah, and the problem is made worse because quoting f
Thank you Alexandre for providing that documentation. I found the last
section on "proxy" makefiles helpful in incorporating the other projects
makefile. I did get it working with this method. For example, I did:
lib_LIBRARIES += libloader.a
libloader.a :
cd cpp/db/loader; \
$(M
On Tue, 27 Jan 2004, Earnie Boyd wrote:
> > Surely the automake maintainers realize that this is a bug, don't they?
> >
>
> No, it is not an automake or autoconf bug. Autoconf and Automake are
> about portability and spaces in path names are not portable.
Which platforms does automake run on whe
Earnie Boyd wrote:
> No, it is not an automake or autoconf bug. Autoconf and Automake are
> about portability and spaces in path names are not portable.
Explain that to some ported-to-unix programs that create
files with spaces in them. It is a matter of custom. On Unix,
the custom is to not d
James Amundson wrote:
On Tue, 2004-01-27 at 06:21, Earnie Boyd wrote:
The usual response to this problem is
_don't_use_path_names_with_spaces_.
Heh heh.
There are different ways to modify
what you are doing that it is not worth modifying the autotools to
handle the space in path name probl
James Amundson <[EMAIL PROTECTED]> writes:
> As far as I can tell, it is impossible to get automake to work with
> pathnames containing spaces. The canonical example is
> ./configure --prefix="/c/Program Files"
> make install
> which will cause make to choke because install will be cal
On Tue, 2004-01-27 at 06:21, Earnie Boyd wrote:
> The usual response to this problem is
> _don't_use_path_names_with_spaces_.
Heh heh.
> There are different ways to modify
> what you are doing that it is not worth modifying the autotools to
> handle the space in path name problem.
Wait a mi
Title: Voyage Vasco
PARDEONNEZ NOUS CETTE INTRUSION...Mais nous sommes convaincus que cette nouvelle va vous intéresser.. et ce sera notre seule intervention sans votre consentement.WWW.VOYAGESARABAIS.COM
Dear friend,
This mail may be a surprise to you because you did not give me the permission to do so
and neither do you know me but before I tell you about myself I want you to please
forgive me for sending the mail without your permission.
My name is Junior Desire Guei, 20 years old an
The usual response to this problem is
_don't_use_path_names_with_spaces_. There are different ways to modify
what you are doing that it is not worth modifying the autotools to
handle the space in path name problem. For instance you could use the
DOS 8.3 modified name which for ``Program Files
13 matches
Mail list logo
