New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #16417 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

tk @8.5.4_0 quartz variant build error on OS X 10.4.11

Reported by: dbueno@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: tk Cc: mww@…, Lars.Rasmusson@…, jann@…, ryandesign@…
Port: tk

Description

The recently-added quartz variant of tk 8.5.4 fails to build on my Intel mac using 10.4.11. Instead I get a log of "error: previous declaration of <some X data structure/function>". The full build log is attached.

There was some discussion here: http://www.nabble.com/Tk-Aqua-variant-gone--td19013676.html#a19013676. In particular Markus Weismann reported that the quartz variant compiled fine on his 10.5/i386 machine. I'm guessing there's probably only a small problem on my machine, but I'm not sure.

Attachments

tk-build-log (23.9 KB) - added by dbueno@… 5 years ago.
Build log with -d
tk-build-log-10.5.5 (32.5 KB) - added by guillaume-jean@… 5 years ago.
port -d install tk +quartz output

Change History

Changed 5 years ago by dbueno@…

Build log with -d

comment:1 Changed 5 years ago by ryandesign@…

  • Owner changed from macports-tickets@… to mww@…

comment:2 in reply to: ↑ description Changed 5 years ago by guillaume-jean@…

Replying to dbueno@…:

The recently-added quartz variant of tk 8.5.4 fails to build on my Intel mac using 10.4.11. Instead I get a log of "error: previous declaration of <some X data structure/function>". The full build log is attached.

There was some discussion here: http://www.nabble.com/Tk-Aqua-variant-gone--td19013676.html#a19013676. In particular Markus Weismann reported that the quartz variant compiled fine on his 10.5/i386 machine. I'm guessing there's probably only a small problem on my machine, but I'm not sure.

I have same issue on 10.5.5 using XQuartz 2.3.1 (xorg-server 1.4.2-apple17). See tk-build-log-10.5.5 attached. Note that it works perfectly when tk is build with universal variant.

Changed 5 years ago by guillaume-jean@…

port -d install tk +quartz output

comment:3 Changed 5 years ago by Lars.Rasmusson@…

  • Cc Lars.Rasmusson@… added

Cc Me!

comment:4 Changed 5 years ago by jann@…

  • Cc jann@… added

Cc Me!

comment:5 Changed 5 years ago by ryandesign@…

  • Cc ryandesign@… added
  • Port set to tk

I see the problem too on 10.4.11 Intel, with tk 8.5.5.

comment:6 Changed 5 years ago by ryandesign@…

r41100 fixes it for me. Update and try it out!

comment:7 follow-up: ↓ 8 Changed 5 years ago by Lars.Rasmusson@…

It worked for me on PPC, 10.5.5. Great work by jann@... !

However, after I had sync:ed the portfiles, neither tcl nor tk were listed by 'port outdated', although I had 8.5.4 installed, and the portfile contained 8.5.5. Does anyone know why?

Also, I suggest that a 'revision' variable is added to the portfile, so that it is clear that the portfile was updated.

comment:8 in reply to: ↑ 7 Changed 5 years ago by ryandesign@…

  • Status changed from new to closed
  • Resolution set to fixed

Replying to Lars.Rasmusson@…:

It worked for me on PPC, 10.5.5. Great work by jann@... !

Great, I'll close the ticket. Please re-open if it's not fixed.

However, after I had sync:ed the portfiles, neither tcl nor tk were listed by 'port outdated', although I had 8.5.4 installed, and the portfile contained 8.5.5. Does anyone know why?

The PortIndex only regenerates every 12 hours.

Also, I suggest that a 'revision' variable is added to the portfile, so that it is clear that the portfile was updated.

The revision only gets incremented when it is necessary to force those who already installed the port to rebuild it. There is no need in this case because either you were already able to install with the +quartz variant (so there's no need to force a rebuild), or if not, then you didn't already have the port installed.

comment:9 Changed 4 years ago by anonymous

  • Milestone Port Bugs deleted

Milestone Port Bugs deleted

comment:10 Changed 4 years ago by lvcargnini@…

I'm having the same problem in Snow Leopard 10.6.1

comment:11 Changed 4 years ago by ryandesign@…

The issue in this ticket was fixed and the ticket closed 11 months ago, and was related to Tiger, so I have a strong feeling the issue you are now experiencing is not the same. Please open a new ticket with more details about exactly what's happening for you.

Note: See TracTickets for help on using tickets.