[ Your messages would be a lot easier to read without the random
schizophrenic line length and indentation. ]
Jay wrote:
> I meant implementing __thread in gcc.
Starting in 4.3 gcc supports emutls, which enables __thread support on
all threaded targets, even when there is no actual TLS support
Is it the source code making the function calls that bothers you,
or the code size/perf bloat?
If it is the source, just hide it with macros, like:
#define foo /* existing thread local stuff */
#define bar /* existing thread local stuff */
typedef struct cygwin_threadlocals_t {
int
Is it the source code making the function calls that bothers you,
or the code size/perf bloat?
If it is the source, just hide it with macros, like:
#define foo /* existing thread local stuff */
#define bar /* existing thread local stuff */
typedef struct cygwin_threadlocals_t {
int
Phil Smith wrote:
exactly what part of "(obviously I can figure this out, but if I knew
offhand it would save me some hassle)" was unclear?
He's saying try it and find out:
$ cat > foo.sh
#!/bin/sh
echo $#
^D
$ chmod +x foo.sh
$ ./foo.sh -Dsomething=c:/Documents and Settings/whatever
3
$ ./foo
: You need this patch:
Ha, thanks for the "very" quick response.
:
: I can't see any mention of the word "debug" in
: http://cygwin.com/faq/faq-nochunks.html#faq.programming.building-cygwin
:
: There is nothing special that needs to be done besides typing "make".
Yes, this links points to the se
Dear All,
I am trying to compile octave-3.0.1-1 on cygwin 1.7
but I am stucked on a different behaviour
of g77 that make the configure scripts unable to
correctly identify the settings for the linking.
This is the extract of config.log on cygwin 1.5
---
co
carlos wrote:
> /oss/src/winsup/cygwin/cygwin.sc:143:
> undefined section `.gnu_debuglink' referenced in expression
That's due to a change in binutils that caused it to be more strict.
The offending line has been removed from the linker script in HEAD. You
can either make the appropriate change
On Tue, Sep 02, 2008 at 03:58:42PM -0400, carlos wrote:
>I am trying to compile cygwin 1.5.25.15.
>I downloaded the source bz2 file (with cygwin setup).
>Extracted it and followed the instructions.
>
>The build goes a long way, until it stops with the following
>message in make.out:
>
>/oss/src/win
I am trying to compile cygwin 1.5.25.15.
I downloaded the source bz2 file (with cygwin setup).
Extracted it and followed the instructions.
The build goes a long way, until it stops with the following
message in make.out:
/oss/src/winsup/cygwin/cygwin.sc:143:
undefined section `.gnu_debuglink' re
On Tue, Sep 02, 2008 at 07:31:01AM +, Jay wrote:
>
> >[jay] harder to port to other architectures,
>> [cgf] Cygwin works on all of the architectures that Windows NT+ supports.
>
>
> I mean really doing a native AMD64 and/or IA64 port, not just relying
> on the ability to run 32bit x86 code. I
(reformatted)
On Tue, September 2, 2008 12:42 am, [EMAIL PROTECTED] wrote:
> Jay <[EMAIL PROTECTED]> wrote:
> snipped the drivel
> ...
>
>> The code seems very wierd in places.
>> I don't "like" it.
>> I know, boo hoo, whine whine whine. It seems to work but it makes me
>> nervous. - Jay
> J
Nose wrote on 02 September 2008 13:14:
> In my previous cygwin version there indeed was
> a make nut in my new installation there wasn't.
Yes, 'make' (and other developer tools) aren't part of the default cygwin
installation - you need to select them explicitly.
> Now it's time to discover th
Thanx very much
Indeed, there was no make.exe present in my cygwin/bin directory and because
of that it
used the make from unixtools. In my previous cygwin version there indeed was
a make nut in my new installation there wasn't.
Now it's time to discover the reason's that the makefile works
On Tue, Sep 2, 2008 at 8:49 AM, Jay <[EMAIL PROTECTED]> wrote:
> 32bit processes can launch 64 bit processes, and vice versa.
> You are not trapped in emulation.
> Simply via the normal CreateProcess, or system(), or ShellExecute().
> There's no need to ask Explorer to do it for you. Except...
On Tue, Sep 2, 2008 at 4:17 AM, Nose wrote:
>
> Okay,
>
> to get serious,
>
> i've got a make script and while executing it gives me the following error:
>
> /cygdrive/d/IonicWork/GDF2TL/Win32bin/MapFil -D dict.opt -V
> ../gdf_out/LUX.tl -Oa ../gdf_out/LUX
> process_begin: CreateProcess((null),
> /
Nose wrote on 02 September 2008 09:17:
> c:\UnxUtils\usr\local\wbin\make.exe: *** [../gdf_out/LUX.vrt.gz] Error 3
That doesn't look like Cygwin make to me.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simpl
wynfield wrote:
I noticed the "--without-xetex" as an agrument to your "Build". What
is the reason for this.
It fails. See texlive and tlbuild lists.
Angelo Graziosi <[EMAIL PROTECTED]> wrote:
^^
Be careful in citing addresses: the spammers are searching them...
Okay,
to get serious,
i've got a make script and while executing it gives me the following error:
/cygdrive/d/IonicWork/GDF2TL/Win32bin/MapFil -D dict.opt -V
../gdf_out/LUX.tl -Oa ../gdf_out/LUX
process_begin: CreateProcess((null),
/cygdrive/d/IonicWork/GDF2TL/Win32bin/MapFil -D dict.opt -V
../
[Robert] Can anyone tell me for sure that it's impossible to run a 64bit
[Robert] windows process from 32bit Cygwin? Or rather.. is it possible to
spawn
[Robert] a 64bit process from Cygwin and have it not be trapped inside WoW64
[Robert] emulation? It seems as though once you're i
Jay,
rather than making silly pedantic and empty arguments I'd rather that you
contributed to making things better. That is if you were truely up to it
capable.
regards
Jay <[EMAIL PROTECTED]> wrote:
snipped the drivel
...
> The code seems very wierd in places.
> I don't "like" it
>[jay] harder to port to other architectures,
> [cgf] Cygwin works on all of the architectures that Windows NT+ supports.
I mean really doing a native AMD64 and/or IA64 port, not just relying
on the ability to run 32bit x86 code. Imho, that's cheating.
> [jay] Why does Cygwin do such wie
Did some more experimenting and Imagemagick fails (dies ) when trying to
convert a
jpg file or a png file to jpg or jp2 format , however a jpg to png works well.
jasper built with or without configuring with "--disable-libjpeg", also died in
a segment faut.
Any ideas of what if the problem?
22 matches
Mail list logo
