Another day, another SCO Compiler Error...
I managed to blow the SCO compiler up again with /contrib/cube. the only
workaround
(from SCO already) is to disable -O on that module.
Fair warning.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Time to install gcc? I believe it's doable for UW.
I haven't touched UW in about 10 years, but I see not much has changed
(I regularly blew up the compiler back then).
andrew
Larry Rosenman wrote:
Show quoted text
I managed to blow the SCO compiler up again with /contrib/cube. the
only workaround
(from SCO already) is to disable -O on that module.Fair warning.
LER
On Sun, 10 Aug 2003, Andrew Dunstan wrote:
Time to install gcc? I believe it's doable for UW.
Yeah, SCO even supplies same. I do get fast turn around, I know
the compiler guys. They are already on the case, and fixing these
2.
I haven't touched UW in about 10 years, but I see not much has changed
(I regularly blew up the compiler back then).
hehe.
andrew
Larry Rosenman wrote:
I managed to blow the SCO compiler up again with /contrib/cube. the
only workaround
(from SCO already) is to disable -O on that module.Fair warning.
LER
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749