There appears to be a slightly annoying bug in latex (and tex) where
they won't support filenames with spaces in.
$latex a\ b.tex
This is TeXk, Version 3.14159 (Web2C 7.4.5)
%&-line parsing enabled.
! I can't find file `a'.
<*> a
b.tex
Please type another input file name:
$latex "a b.tex"
Th
Christian Rudiger wrote:
Hello Al,
thank you, it worked.
i putted one at the end of the program just writing :
}; // end of class
int main(){}
why does that work? I think thats strange.
Regards Christian Rudiger
I thought I would post this to the list, because it's nice to have
complete dicussion
electa wrote:
i have used
#include
but gcc still prints
"implicit declaration of function lrand48()",
and "srand48()".
Just checking, are you using the "-mno-cygwin" flag on gcc/g++? This
would cause that error. If so, then you are using mingw and should
really go and ask them why it doesn't
utomo wrote:
And also better if the setup can download simultaneusly, or preparing
for the next file.
Now if we look at the download process, the connecting time (for each
file) is consuming time. If the download process can reduce this, I
believe the download will be much faster.
A much mo
Jim Scheef wrote:
Dave and all,
I have been trying for weeks to find a way to sort these messages in
the Netscape 7 version of Mozilla Mail. Nothing has worked. Adding a
consistent flag to the subject line like [cygwin] would make the
sorting trivial. If it took the list administrator 15 minut
...
Hi self!
I've been having a play around and I believe this problem is connected
to #include_next not respecting the -mno-cygwin. My knowledge of gcc is
however nowhere near enough for me to be sure. I just wanted to say this
to perhaps save someone else some small amount of time.
Chris
-
Volker Quetschke wrote:
Hi, could someone please confirm that this is a bug, and not a
problem that exists only on this computer.
Thanks
Volker
Volker Quetschke wrote:
Hi,
when I use the following command gcc finds the wrong include
file.
$ echo "#include " | gcc -mno-cygwin -E -
# 1 ""
Alex Vinokur wrote:
"chris" wrote in message news:[EMAIL PROTECTED]
Alex Vinokur wrote:
Comparative Performance of C++ Compilers
C/C++ Performance Tests
=
While this is quit
Hans Horn wrote:
I light of the recent gcc performance comparison, I tried to compile a
number crunching application (for which I have noticed a significant
performance degradation of a factor 2-3 since the days of gcc2.9.x) using
the -mno-cygwin flag.
I get a shitload of crap like the following :
Ken Thompson wrote:
I don't think the behavior should be changed. d2u stands for dos to unix
which means \r\n to \n. Why would one expect a dos to unix utility to
convert mixed line terminator files. If you need such a utility, then add
one but don't take a utility that does dos to unix and try
Gareth Pearce wrote:
As obviously you're a mailing list professional, I'm sure you checked the
mailing list archives before posting on this topic.
Hence there is no need for me to reply.
As implied by my above statement, the topic has already been discussed.
Therefore given the subject line of th
Cygwin includes quite a number of symlinks. I personally have changed a
number of the cygwin-style symlinks to windows-style ones to fix (as has
been mentioned recently) the problem that cygwin-style symlinks don't
work from cmd
Would it be possible to automagically change all the cygwin-style
Hello.
I suspect that this is a FAQ, but I haven't found it, so I'll ask it!
Unlike linux / *BSD / etc distributions, it doesn't seem easy to
automate the cygwin install utility. I don't seem able to get a list of
installed packages, give a package to install from a given file, examine
the pac
Igor Pechtchanski wrote:
On Wed, 28 Jan 2004, zzapper wrote:
Hi Y'All
Anyone investigated putting a cutdown version of CygWin onto a memory
stick (128MB or bigger).
What would you need the dlls vim,find,grep,ls etc??
zzapper (vim & cygwin & zsh)
Sure. Google for "Cygwin on CD". Some is
Hello!
I've recently found that latex has begun crashing if I execute it from a
windows xp (or 2000) cmd prompt.
It happens by simply typing "latex" at a cmd prompt. I get (in a windows
error box)
16 bit MS-DOS Subsystem
C:\WINDOWS\System32\cmd.exe - latex
The NTVDM CPU has encountered an ill
15 matches
Mail list logo