On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> If I read the code, it seems like there's something funky with the first
> variable argument. What I have for now is:
>
> -Tcl_AppendResult(Tcl_Interp *interp, char *p, va_alist)
> +void Tcl_AppendResult(Tcl_Interp *inte
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> If I read the code, it seems like there's something funky with the first
> variable argument. What I have for now is:
>
> -Tcl_AppendResult(Tcl_Interp *interp, char *p, va_alist)
> +void Tcl_AppendResult(Tcl_Interp *inte
Thanks, I'm using a more up to date version right now. I seem to have
averted the problem of varargs; there's only 1 instance thats not in
tcl/. Now the next problem is that the window initialization doesn't
called called, and so xres=yres=0, which is a floating point exception..
Thanks,
--
Just
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> The code uses which gcc-3.3 doesn't support. is
> the new standard. I've done my best to convert the code, but I can't
> solve a crash in the of the functions I had to change.
This is the right approach, and your efforts are bet
On Sat, Jul 31, 2004 at 06:02:56PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> > On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > > story see below..
Thanks, I'm using a more up to date version right now. I seem to have
averted the problem of varargs; there's only 1 instance thats not in
tcl/. Now the next problem is that the window initialization doesn't
called called, and so xres=yres=0, which is a floating point exception..
Thanks,
--
Just
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> The code uses which gcc-3.3 doesn't support. is
> the new standard. I've done my best to convert the code, but I can't
> solve a crash in the of the functions I had to change.
This is the right approach, and your efforts are bet
On Sat, Jul 31, 2004 at 06:02:56PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> > On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > > story see below..
Justin Pryzby <[EMAIL PROTECTED]> writes:
> The code uses which gcc-3.3 doesn't support. is
> the new standard. I've done my best to convert the code, but I can't
> solve a crash in the of the functions I had to change.
> See va_arg(3) for a reference. Here's what I did:
> - C
On Sun, Aug 01, 2004 at 03:10:52AM +0200, Frank Lichtenheld wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > Hi all,
> >
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
>
> Hmm, what is upstream saying about the mess? Th
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> Hi all,
>
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
Hmm, what is upstream saying about the mess? That's the point I missed
in the story.
Gruesse,
--
Frank Lichtenheld <[EMAIL PRO
On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
>
> > gcc includes /usr/bin/gcc which is pretty much a necessity, I thi
On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
> > gcc includes /usr/bin/gcc which is pretty much a necessity, I thin
Justin Pryzby wrote:
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
>
> gcc includes /usr/bin/gcc which is pretty much a necessity, I think.
> I need xmkmf to work too. For now I have Build-Depends: gcc-3.2, but
> what can I do to force it to actuall
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
> gcc includes /usr/bin/gcc which is pretty much a necessity, I think. I
> need xmkmf to work too. For now I have Build-Depends: gcc-3.2, b
Hi all,
I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
story see below..
gcc includes /usr/bin/gcc which is pretty much a necessity, I think. I
need xmkmf to work too. For now I have Build-Depends: gcc-3.2, but what
can I do to force it to actually compile with that, in
Justin Pryzby <[EMAIL PROTECTED]> writes:
> The code uses which gcc-3.3 doesn't support. is
> the new standard. I've done my best to convert the code, but I can't
> solve a crash in the of the functions I had to change.
> See va_arg(3) for a reference. Here's what I did:
> - C
On Sun, Aug 01, 2004 at 03:10:52AM +0200, Frank Lichtenheld wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > Hi all,
> >
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
>
> Hmm, what is upstream saying about the mess? Th
On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
>
> > gcc includes /usr/bin/gcc which is pretty much a necessity, I thi
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> Hi all,
>
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
Hmm, what is upstream saying about the mess? That's the point I missed
in the story.
Gruesse,
--
Frank Lichtenheld <[EMAIL PRO
On Sat, Jul 31, 2004 at 05:58:53PM -0700, Steve Langasek wrote:
> On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> > I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> > story see below..
> > gcc includes /usr/bin/gcc which is pretty much a necessity, I thin
On Sat, Jul 31, 2004 at 08:39:52PM -0400, Justin Pryzby wrote:
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
> gcc includes /usr/bin/gcc which is pretty much a necessity, I think. I
> need xmkmf to work too. For now I have Build-Depends: gcc-3.2, b
Justin Pryzby wrote:
> I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
> story see below..
>
> gcc includes /usr/bin/gcc which is pretty much a necessity, I think.
> I need xmkmf to work too. For now I have Build-Depends: gcc-3.2, but
> what can I do to force it to actuall
Hi all,
I have a package (x11iraf) which conflicts with gcc-3.3. For the whole
story see below..
gcc includes /usr/bin/gcc which is pretty much a necessity, I think. I
need xmkmf to work too. For now I have Build-Depends: gcc-3.2, but what
can I do to force it to actually compile with that, in
24 matches
Mail list logo