Re: Bug
От | Vincent Predoehl |
---|---|
Тема | Re: Bug |
Дата | |
Msg-id | B44169DB-BEE9-4C53-9665-C31F4DB852D1@gmail.com обсуждение исходный текст |
Ответ на | Re: Bug (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-bugs |
On Dec 30, 2008, at 2:49 AM, Peter Eisentraut wrote: > Vincent Predoehl wrote: >> On Dec 20, 2008, at 9:15 AM, Peter Eisentraut wrote: >>> On Saturday 20 December 2008 02:15:05 Vincent Predoehl wrote: >>>> On Dec 19, 2008, at 3:48 AM, Peter Eisentraut wrote: >>>>> Vincent Predoehl wrote: >>>>>> I was running fink and it said to report this: >>>>>> configure: WARNING: krb5.h: present but cannot be compiled >>>>>> configure: WARNING: krb5.h: check for missing prerequisite >>>>>> headers? >>>>>> configure: WARNING: krb5.h: see the Autoconf documentation >>>>>> configure: WARNING: krb5.h: section "Present But Cannot Be >>>>>> Compiled" >>>>>> configure: WARNING: krb5.h: proceeding with the preprocessor's=20=20 >>>>>> result >>>>>> configure: WARNING: krb5.h: in the future, the compiler will take >>>>>> precedence >>>>>> configure: WARNING: ## >>>>>> ---------------------------------------- ## >>>>>> configure: WARNING: ## Report this to pgsql- >>>>>> bugs@postgresql.org <mailto:pgsql-bugs@postgresql.org> ## >>>>>> configure: WARNING: ## >>>>>> ---------------------------------------- ## >>>>> >>>>> Which PostgreSQL version? >>>> >>>> 8.3.5 >>> >>> Could you attach your config.log file then? >> Here it is. I ran ./configure since I posted the error occurred=20=20 >> because I was having problems with my system =85 it didn't reboot=20=20 >> after the last update. Hopefully, this will give you the info=20=20 >> you're looking for. Let me know if I can be of further assistance. > > This is not the config.log file from the run that produced the=20=20 > warning you are complaining about. One other thing, I have tried to use fink ( MacOS X ) to install=20=20 postgresql, but reverted to downloading the source myself because the=20=20 non-standard directory structure that fink created for the package=20=20 was causing problems. I'll see if I can reproduce the error. --=20 Vincent
В списке pgsql-bugs по дате отправления: