Opened 14 years ago

Closed 14 years ago

#302 closed defect (worksforme)

trunk build fails

Reported by: darkblueb Owned by: geos-devel@…
Priority: major Milestone:
Component: Default Version: main
Severity: Unassigned Keywords:
Cc:

Description

debian 5.03 Linux aced 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC 2009 x86_64 GNU/Linux

there is something amiss with the overlay dir.. make fails saying there is no rule to make FuzzyPointLocator, the first of three files there by creating sym links in the parent dir to the 3 cpp files, you can fool make to complete but then a similar and parallel fail happens with make check -- g++ -DHAVE_CONFIG_H -I. -I../../source/headers -I../../source/headers/geos -I../../source/headers -I../../tests/unit/tut -I../../capi -g -O2 -DGEOS_INLINE -pedantic -Wall -ansi -Wno-long-long -ffloat-store -MT IsSimpleOpTest.o -MD -MP -MF .deps/IsSimpleOpTest.Tpo -c -o IsSimpleOpTest.o test -f 'operation/IsSimpleOpTest.cpp' || echo './'operation/IsSimpleOpTest.cpp mv -f .deps/IsSimpleOpTest.Tpo .deps/IsSimpleOpTest.Po make[3]: * No rule to make target operation/overlay/FuzzyPointLocatorTest.cpp', needed by FuzzyPointLocatorTest.o'. Stop.

Change History (4)

comment:1 by pramsey, 14 years ago

Resolution: invalid
Status: newclosed

Remember to ./autogen and ./configure after updates that touch the build system.

in reply to:  1 comment:2 by darkblueb, 14 years ago

Resolution: invalid
Status: closedreopened

Replying to pramsey:

Remember to ./autogen and ./configure after updates that touch the build system.

a little premature close there .. this is a new set of sources and I did autogen and configure, thx

comment:3 by pramsey, 14 years ago

Got nothing for you then, since to confirm current state I did the same thing on my system (checkout, gen, config, build) and everything ran to completion. Can you work back to a commit that caused the state change?

in reply to:  3 comment:4 by darkblueb, 14 years ago

Resolution: worksforme
Status: reopenedclosed

Replying to pramsey:

Got nothing for you then, since to confirm current state I did the same thing on my system (checkout, gen, config, build) and everything ran to completion. Can you work back to a commit that caused the state change?

just when you think you have it, dept. rev. 2748 now working...

Note: See TracTickets for help on using tickets.