Обсуждение: Mac OS X make check errors...
Hi all,
I just tried the newest beta (3) and for the first
time I am getting multiple errors in 'make check'.
this is my configure line...
./configure --with-rendezvous --enable-thread-safety
--disable-shared
I inserted the --disable-shared from a recomendation
to not create the shared libraries as i use libpq.a
exclusively.
I will see if removing it helps.
Is there something I should be aware of?
Ted
parallel group (7 tests): create_aggregate
create_operator triggers vacuum constraints inherit
create_misc
constraints ... ok
triggers ... FAILED
create_misc ... ok
create_aggregate ... ok
create_operator ... ok
inherit ... ok
vacuum ... ok
parallel group (2 tests): create_view create_index
create_index ... ok
create_view ... ok
test sanity_check ... ok
test errors ... ok
test select ... ok
parallel group (18 tests): select_distinct_on update
select_having select_distinct select_into union case
namespace random select_implicit aggregates hash_index
arrays transactions portals btree_index join subselect
select_into ... ok
select_distinct ... ok
select_distinct_on ... ok
select_implicit ... ok
select_having ... ok
subselect ... ok
union ... ok
case ... ok
join ... ok
aggregates ... ok
transactions ... FAILED
random ... ok
portals ... ok
arrays ... ok
btree_index ... ok
hash_index ... ok
update ... ok
namespace ... ok
test privileges ... ok
test misc ... ok
parallel group (5 tests): portals_p2 select_views
cluster rules foreign_key
select_views ... ok
portals_p2 ... ok
rules ... ok
foreign_key ... ok
cluster ... ok
parallel group (14 tests): limit copy2 sequence
truncate temp polymorphism conversion prepare domain
rowtypes rangefuncs plpgsql without_oid alter_table
limit ... ok
plpgsql ... failed (ignored)
copy2 ... FAILED
temp ... ok
domain ... ok
rangefuncs ... FAILED
prepare ... ok
without_oid ... ok
conversion ... FAILED
truncate ... ok
alter_table ... ok
sequence ... ok
polymorphism ... ok
rowtypes ... ok
test stats ... FAILED
test tablespace ... ok
============== shutting down postmaster
==============
postmaster stopped
====================================================
7 of 96 tests failed, 1 of these failures ignored.
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
On Mon, 2004-10-18 at 12:55, Theodore Petrosky wrote: > I just tried the newest beta (3) and for the first > time I am getting multiple errors in 'make check'. Can you post the regression.diffs file produced by "make check" (should be in src/test/regress under the directory in which you build PostgreSQL). -Neil
Theodore Petrosky <tedpet5@yahoo.com> writes:
> I just tried the newest beta (3) and for the first
> time I am getting multiple errors in 'make check'.
> this is my configure line...
> ./configure --with-rendezvous --enable-thread-safety
> --disable-shared
> ...
> 7 of 96 tests failed, 1 of these failures ignored.
--disable-shared means you do not get any of the backend extensions that
come as shared libraries; this includes plpgsql (and the other PL
languages if you had tried to build 'em) as well as character set
conversions. I think the tests that failed are exactly the ones that
depend on plpgsql or conversions.
I notice that pg_regress.sh has a kluge to cause it to ignore the
failure of the plpgsql regression test when --disable-shared is true,
but this seems a totally lost cause with so many other tests now making
use of that language. I propose taking out that special case.
Peter, I think you were the one who put in the special case to begin
with; do you have any better ideas?
regards, tom lane
On Tue, 2004-10-19 at 10:36, Tom Lane wrote: > --disable-shared means you do not get any of the backend extensions that > come as shared libraries; this includes plpgsql (and the other PL > languages if you had tried to build 'em) as well as character set > conversions. I think the tests that failed are exactly the ones that > depend on plpgsql or conversions. Just to confirm, Theodore sent me the regression.diffs via private mail and that is indeed the problem (plpgsql is not getting created). -Neil
I only added the --disable-shared from a recommendation on the cocoa developers forum. Someone reported problems using libpq.a and the solution offered was the above. The original person spoke of problems linking libpg.a. The poster mentioned something about even though he specified the libpg.a, the linker was finding the dynamic library. I can neither confirm nor deny this finding. Here is the original post.... I have a cocoa application that I link against a postgresql library. There appear to be two libraries to choose from libpq.a and libpg3.2.dylib I picked libpq.a in Xcode but otool shows that the compiled program will use libpg3.2.dylib Is there a way I can have the linker do a static link for this one library? ( ie use libpq.a ) (I am currently using ver 8.0.0b3 for postgresql but most of the world is using version 7.x.x) ___________ and the answer from the same person...... It appears that the linker will choose a dylib over an archive lib. I got around the problem by moving the dylibs out of the directory containing libpq.a and then was able to get the libpq to be staticly linked into the image. The only one I could get libpq.a into the build process was to drag the file onto the project. Then open panel in the add file to project would not let me choose the static library. I guess I will need to keep a copy of the static lib in some other directory... ___________ and the answer from another source... If you do: ./configure --disable-shared You can build without getting the dylib. - Scott --- Tom Lane <tgl@sss.pgh.pa.us> wrote: > Theodore Petrosky <tedpet5@yahoo.com> writes: > > I just tried the newest beta (3) and for the first > > time I am getting multiple errors in 'make check'. > > > this is my configure line... > > ./configure --with-rendezvous > --enable-thread-safety > > --disable-shared > > ... > > 7 of 96 tests failed, 1 of these failures > ignored. > > --disable-shared means you do not get any of the > backend extensions that > come as shared libraries; this includes plpgsql (and > the other PL > languages if you had tried to build 'em) as well as > character set > conversions. I think the tests that failed are > exactly the ones that > depend on plpgsql or conversions. > > I notice that pg_regress.sh has a kluge to cause it > to ignore the > failure of the plpgsql regression test when > --disable-shared is true, > but this seems a totally lost cause with so many > other tests now making > use of that language. I propose taking out that > special case. > > Peter, I think you were the one who put in the > special case to begin > with; do you have any better ideas? > > regards, tom lane > _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com