with that value. It probably should check only for
bison, and abort on error if it is not found.
Alternatively, bison can be manually run on the .y and the resultant y.tab
can be checked in to CVS.
--
-- Todd Vierling <[EMAIL PROTECTED]>
le
machines; one compiler looking at multiple sets of .h and shared libraries
is enough.
--
-- Todd Vierling <[EMAIL PROTECTED]>
down to is this: NetBSD doesn't do all the kernel and libc
shuffling of Linux. Its version numbers are quite well defined, and it's
trivial to state what version was used to compile a binary. So the patch is
Just Fine as-is, and needs no further pollution.
--
-- Todd Vierling <[EMAIL PROTECTED]>
where such a
check can be done with low impact, but these cases should be evaluated
carefully and kept in the "rare" category as much as possible.
--
-- Todd Vierling <[EMAIL PROTECTED]>
check, and you sacrifice
*maintainability* with the extra normally-dead code added to Wine. I don't
see a need to jump through extra hoops in this case.
--
-- Todd Vierling <[EMAIL PROTECTED]>
used to compile, and all later versions.
--
-- Todd Vierling <[EMAIL PROTECTED]>
's not an optional kernel feature.
(Besides all this, detecting this particular feature at runtime is ...
difficult at best. The "protected" memory range is different depending on
the CPU platform.)
--
-- Todd Vierling <[EMAIL PROTECTED]>
back and forth on kernel
versions is a glaring exception to this common-sense rule. 8-)
--
-- Todd Vierling <[EMAIL PROTECTED]>
ems, so binaries compiled with older
headers still work even if the kernel supports MAP_TRYFIXED. (They'll just
be slower. 8-)
--
-- Todd Vierling <[EMAIL PROTECTED]>
for system
libraries, mind you, not Wine's own) through.
Hm. I can remake the patch with a path strip expression, if that would suit
you.
--
-- Todd Vierling <[EMAIL PROTECTED]>
On Thu, 24 Jul 2003, Todd Vierling wrote:
: Because this patch deals mostly with handling of whitespace and tabs, I've
: included a uuencoded version of the diff as well.
...And it would have been better if I had attached a correct copy of the
diff (there were missing m4 quote-brackets i
A work-around is to use Xvfb as the X server.
That's so bloated, that it's like working around a family feud by bombing
the other family out of existence. But since my last name isn't Bush, I
don't think that's very useful. 8-P
--
-- Todd Vierling <[EMAIL PROTECTED]>
map that simulated a 32-bit memory
space, thus essentially making an Alpha behave much like an x86 -- well,
sort of.
A Wine compiled as Win64 will likely not be able to run Alpha NT binaries.
However, it might work reasonably well to compile apps with Winelib.
--
-- Todd Vierling <[EMAIL PROTECTED]>
before it was pruned out for LP64 usage.
To do this correctly per the C standard, cast to an integer of at least the
pointer's size (intptr_t), and then cast it further down:
For the first case,
((intptr_t)id >> 16)
For the second one,
(UINT16)(intptr_t)id
--
-- Todd Vierling <[EMAIL PROTECTED]>
on all
typical ILP32 and LP64 hosts.
--
-- Todd Vierling <[EMAIL PROTECTED]>
o roll the frills of ttydrv into x11drv and do away with multiple
driver selection altogether. (Keeping it simple?)
--
-- Todd Vierling <[EMAIL PROTECTED]>
to do with the scope of the thread. This
isn't "mklinux-devel".
--
-- Todd Vierling <[EMAIL PROTECTED]>
#x27; ||
: (*ptr == '\r'&& *(ptr + 1) == '\n'));
Could overrun the buffer by looking one char too far if the last character
of the file is '\r'.
--
-- Todd Vierling <[EMAIL PROTECTED]>
correctly,
This assumes that having a / mapping is not configuring Wine "correctly".
If Wine is to be integrating Windows apps into the Unix environment, mapping
/ to some drive letter should indeed be "correct" configuration.
--
-- Todd Vierling <[EMAIL PROTECTED]>
y configure / install Wine (and who do not understand the 'Drive'
: error message).
I see mapping a drive to `/' as `proper' configuration. (i.e. If Wine is
meant to integrate apps to the Unix environment, it shold be able to see
the full Unix environment.)
--
-- Todd Vierling <[EMAIL PROTECTED]>
n address the fact that Winelib apps (say, a virus), can
access native system shared libraries. A quick call to dlopen(3) followed
by dlsym(3) and
--
-- Todd Vierling <[EMAIL PROTECTED]>
by Carlos: you will have read access on special files/devices
: (Z:\dev\hda*, Z:\dev\fd0, ...)
And the problem with that is? (I suspect FUD, again.)
--
-- Todd Vierling <[EMAIL PROTECTED]>
Arbitrary Unix OS mounts removable
media. For one, I know mine doesn't. 8-)
--
-- Todd Vierling <[EMAIL PROTECTED]>
ience to be able
to use a Windows program on an arbitrary file. (I put in my / mapping when
I needed to run MS Media Sprayer on a group of files for an obscure
Windows-only codec, and didn't want either to move the files around or
create a specialized mapping for just that file group.)
r Unix commands can't
Now, if someone would like to offer a *technically competent* argument as to
why mapping a drive letter to / is bad, I'd love to hear it.
--
-- Todd Vierling <[EMAIL PROTECTED]>
25 matches
Mail list logo
