ereas mine did not.
I would encourage you to submit this patch directly to the gettext
maintainer(s), as it really needs to go in there too.
Thanks,
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Bui
using --disable-nls.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
-- Forwarded message
ed in the gimp README or elsewhere, it should
be. It tripped me up a while back too.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building (701) 231-8541 (Fax)
North Dakota State Univers
icks that you used because in general that could result
in a "line too long" problem, on many UNIXes. My method is slower by a
lot because it will exec egrep for every file in the list, but it will
never fail because of too many files. Probably not an issue in this case,
so yours might
In regard to: Re: TODO for 1.2 release, Austin Donnelly said (at 11:35pm on...:
>On Tuesday, 26 Sep 2000, Tim Mooney wrote:
>
>> @@ -2322,6 +2322,7 @@
>>G_IO_ERROR_NONE,
>>G_IO_ERROR_AGAIN,
>>G_IO_ERROR_INVAL,
>> + G_IO_ERROR_INTR,
>>
'*.c' -o -name '*.h' -exec egrep '//' {} /dev/null \; | \
grep -v '://'
(to get rid of false matches on URLs)
> didn't work as I would have expected it. Will grep it manually and
> replace every C++ comment by a C comment. Thanks for point
In regard to: Re: TODO for 1.2 release, [EMAIL PROTECTED] said (at 12:05am on...:
>On 26 Sep, Tim Mooney wrote:
>
>> I'll try build 1.1.26 or some subsequent release on the platforms I
>> have access to, but whoever does pre-release builds (Yosh?) should see
>>
tforms I have
access to, but whoever does pre-release builds (Yosh?) should see if there's
a way to make your compiler (gcc?) warn/error on C++ style comments. Every
single point build of gimp for the last dozen or so builds has included
new C++ style comments i
def any debug scribble to console
>> 100. Check package files, READMEs, etc. for correctness
>>
>
>??. sigaction/OSF/1/GTK resolution
>Signal messiness. and a temporary hack is (Am I correct on this, Tim Mooney?)
I was going to send something to the list about this very issue.
orted this in various places since October
of last year, but haven't had much luck getting people interested in fixing
the problem. Since gtk+, gimp, and many of the GNOME packages have become
better about honoring --disable-nls, that's the route I've been taking lately.
Tim
--
Tim
In regard to: Re: urgent please, Tomas Ogren said (at 9:41am on Aug 14, 2000):
>On 13 August, 2000 - Tim Mooney sent me these 2.6K bytes:
>
>> Basically, the way gtk is built on AIX makes it pretty much unusable, because
>> of the way AIX does shared object dependencies. Th
ere), if
that's what the gtk+ developers think the best solution is for the time being.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
gv = 0x2ff22c88), line 132 in "main.c"
>(dbx)
I get the same thing. As I think I've said before, my guess is it's a
gtk problem, but that's just a wild guess.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (7
nd search by package for
gimp
Wander around on
http://www.gimp.org
to find the info on how to get the CVS version.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building
ent development versions of the gimp also exhibit gtk+ problems
on AIX. Whether that's because of a bug in gtk+ or a bug in AIX is unknown
at this point.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
ink gdb 5.x might work, but can't remember for sure.
In any case, there's definitely a problem there, but it may be in gtk+ and
not in gimp itself. Or it could be in AIX 4.3.x...
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services
lly different from the old one except
>that it uses sigaction()) works as expected.
>
>I guess Tim with his hardware zoo will be able to answer the question :)
I'll be checking it this weekend, and I'll definitely report to the "signal
crew" on my findings. :-)
Tim
--
Tim M
In regard to: Re: EPIPE, Nick Lamb said (at 2:57am on May 11, 2000):
>On Wed, May 10, 2000 at 07:15:57PM -0500, Tim Mooney wrote:
>> Finding a processor/OS combo where sizeof(pointer) != sizeof(int) is pretty
>> easy, however. How does this change your thinking?
>
>Wouldn&#
x27;s it. Is that what
you were trying to say? Since you apparently have access to Stevens' APUE,
look at section 10.7 again if you don't understand what I'm talking about.
You're definitely correct that gimp shouldn't be mucking with SIGCLD, and
it's not.
Tim
-
t the plug-in protocol detect
the problem (assuming it can?)?
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J1, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
vestigate the handler in 1.1.19 or earlier, and see what was being
done on SIGPIPE there.
Austin is also correct that calling printf from the handler is probably
asking for trouble. If a message must be written, some other method should
be found (write *is* ok from a signal handler, but won'
;ve submitted
via email to [EMAIL PROTECTED] since 1.1.20 came out have not resulted in
any email notification yet. I'm suspicious they ended up in the bit bucket.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 2
sfully and work as expected thereafter.
At that point, you can run gimp without tracing it, and the plugins work fine.
It's only the first time through that this happens.
It's definitely an odd problem. If anyone has any suggestions for how to
debug it, please let me know. I wou
In regard to: Re: Crash in Gimp 1.1.7 on Solaris 8., Ludovic Poitou said...:
>Tim Mooney wrote:
>
>> In regard to: Crash in Gimp 1.1.7 on Solaris 8., Ludovic Poitou said (at...:
>>
>> >signal BUS (invalid address alignment) in color_pixels at 0x177858
>> >
> while (w--)
> {
> for (b = 0; b < bytes; b++)
> dest[b] = color[b];
>
> dest += bytes;
> }
> }
> }
>}
I'm not sure what the right fix is, being I haven't looked long enough at
the code to decipher what's going on. Th
In regard to: Re: Print plug-in, Glyph Lefkowitz said (at 3:24pm on Feb 1,...:
>
>On Tue, 1 Feb 2000, Tim Mooney wrote:
>
>> I agree that would be the best solution, but I'm afraid it's not that
>> easy. I've submitted quite a few very small portability patch
erson that's had much the same experience, though I think they were more
tenacious than I was, and after quite a bit of arguing they did get some
of their patches integrated into CVS.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services
up again and threaten to
>> code a replacement Kim*g*sh*p if we won't re-write Gimp in C++ :)
>
>The world doesn't live just on Linux. Gimp runs on other platforms.
Amen. :-)
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services
possible
further investigate. I looked briefly at both reports, and I don't think
#3414 is happening any more (I think as of 1.1.13), but I will verify.
I can tell you that although it hasn't been reported, I get script_fu to
SEGV on startup every time.
I will report back this weekend
In regard to: Re: Re: Tile Cache Size, Marc Lehmann said (at 1:05am on Nov...:
>On Mon, Nov 01, 1999 at 08:04:39PM -0600, Tim Mooney
><[EMAIL PROTECTED]> wrote:
>> Wouldn't the situation be even worse, then, if we're going through the
>> filesystem and there&#x
r_ how fast your
>physical swap may be (for linear r/w).
Wouldn't the situation be even worse, then, if we're going through the
filesystem and there's "average" fragmentation? You seem to be assuming that
the filesystem allocation will be contiguous (or at least close) on disk
*: getpwuid_r(): failed due to: Function not implemented.
>Message: Passed serialization test
>
>./gimp: fatal error: sigsegv caught
>./gimp (pid:6161): [E]xit, [H]alt, show [S]tack trace or [P]roceed:
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Se
32 matches
Mail list logo
