PostgreSQL version 8.2 was officially released yesterday (12/5/2006). Among the new features are a nice performance increase and online index building.
I tried modifying the 8.1.5 ebuild but I'm running in to problems with the autoconf test for threading.
To clarify: my problems occurred while trying to build dev-db/libpq (the client libraries), before the postgresql build would even happen.
Okay, I've got this building now. The thread problem was actually caused by libpq failing to download and extract the postgresql-test tarball, which is needed to pass all the confgure tests for threading. By adding that to the source URI's libpq now builds. I'll upload the ebuild I used for that, and if I can get the postgresql to complete successfully, I'll upload that next.
Created attachment 103512 [details] libpq ebuild, requires libpq-8.2.0-gentoo.patch, which can be copied from libpq-8.1.5-gentoo-patch
Created attachment 103513 [details] First pass at postgresql patch My first postgresql patch requires some work to make sure that no tests are run (or needed) if the "test" use flag is not enabled. Changes in the 8.2.0 build cause tests to run even if "-test" is set.
Note that several files from the 8.1.5 file set need to be copied and renamed for 8.2.0. They are: postgresql-8.2.0-gentoo.patch, postgresql.conf-8.2, and postgresql.init-8.2.
These ebuilds are working for me, both on x86 and amd64.
so this ebuild does not require libpq-8.2.0? also, will these be added to postgresql overlay or portage?
No, this requires libpq-8.2.0. That ebuild is included as well. As for whether these will make the posgresql overlay, I have no idea as I am not involved in the overlay.
any hope to see an official postgresql 8.2 ebuild in portage? how about pgadmin III 1.6.1 ebuild? how about pgadmin3-adminpack ebuild? and fix emerge --config =postgresql problem so we can specify template0 encoding etc? why is postgresql lagging so much behind in Gentoo? Even Windows has all of that available....
(In reply to comment #10) > any hope to see an official postgresql 8.2 ebuild in portage? Sure, just not soon, we're atm working on other issues first, like the other PgSQL versions etc. > how about pgadmin III 1.6.1 ebuild? PgAdmin 1.6.X needs wxGTK-2.7, which isn't in Portage yet, we have ebuilds for PgAdmin 1.6.X ready, but can't ad > how about pgadmin3-adminpack ebuild? Use the overlay, will probably be added with 1.6.X when it's time. > and fix emerge --config =postgresql > problem so we can specify template0 encoding etc? There is no problem there, it works, it just lacks additional, optional settings... We're working also on this, slowly... > why is postgresql lagging so much behind in Gentoo? Even Windows has all of > that available.... Cause it's atm two people doing all the work, people who have other responsibilities and a thing called "real life" too, so please be patient OR help us with patches that add the features you want/need OR use the OS you mentioned above. :) Best regards, CHTEKK.
I can help with testing. I have both x86 and amd64 machines. I can also provide a server or two for testing or development if needed. Let me know how I can help (I don't write ebuilds but know Gentoo inside and out). (In reply to comment #11) > (In reply to comment #10) > > any hope to see an official postgresql 8.2 ebuild in portage? > > Sure, just not soon, we're atm working on other issues first, like the other > PgSQL versions etc. > > > how about pgadmin III 1.6.1 ebuild? > > PgAdmin 1.6.X needs wxGTK-2.7, which isn't in Portage yet, we have ebuilds for > PgAdmin 1.6.X ready, but can't ad > > > how about pgadmin3-adminpack ebuild? > > Use the overlay, will probably be added with 1.6.X when it's time. > > > and fix emerge --config =postgresql > > problem so we can specify template0 encoding etc? > > There is no problem there, it works, it just lacks additional, optional > settings... We're working also on this, slowly... > > > why is postgresql lagging so much behind in Gentoo? Even Windows has all of > > that available.... > > Cause it's atm two people doing all the work, people who have other > responsibilities and a thing called "real life" too, so please be patient OR > help us with patches that add the features you want/need OR use the OS you > mentioned above. :) > Best regards, CHTEKK. >
Okay, if you need help - I'll attach ebuilds for 8.2.0 libpq and postgresql. Not sure if it's mostly or completely based on the current portage, because I was looking at overlay as well and got confused with all the exprimental, testing, etc. I might have borrowed something from overlay ebuilds, not sure. I hope it's okay if I attach those as tarballs, since there are quite a few files there.
Created attachment 104137 [details] dev-db/libpq ebuild libpq
Created attachment 104138 [details] dev-db/postgresql ebuild postgresql
Michael Krelin, can you highlight the differences between your ebuilds and the ones I already uploaded?
Chrostopher, sure, yours are, basically, quick way to get postgresql 8.2.0 on your system and serve their purpose. I took care of libpq SLOT, patches, especially ones related to test phase. Those should be quite suitable for putting into portage with no or minimal changes. I would not recommend anyone who merged your ebuilds to switch to mine, yours should work fine (well, maybe it makes sense because libpq SLOT), but I really want to see this version of postgres in portage and I'm trying to provied as much assistance as I can to those two guys with other responsibilities and even real life. No hard feelings? ;-)
No hard feelings. I was just trying to learn from your changes.
Just to make sure ;-) I really hope we will see it in portage soon now. While all the reasons are understandable, the lag is tremendous... As for the changes: as I outlined before, the most important ones are related to make test phase work (and disable it when not needed too as you pointed out). That is where old patches do not work since postgres guys rewrote regression test shell script in C. And the other important thing is that as I understand SLOT for libpq should follow libpq major version number which is 5 for this release. Let's hope this description will save maintainers time as well.
(In reply to comment #19) > Just to make sure ;-) I really hope we will see it in portage soon now. While > all the reasons are understandable, the lag is tremendous... Yeah, 11 days. That's tremendous. > > As for the changes: as I outlined before, the most important ones are related > to make test phase work (and disable it when not needed too as you pointed > out). That is where old patches do not work since postgres guys rewrote > regression test shell script in C. And the other important thing is that as I > understand SLOT for libpq should follow libpq major version number which is 5 > for this release. And here comes the problem: The existing slotting is broken. There are file-collisions between the different slots of libpq. And we're preparing a new slotting (also for the server) which will work. This stuff is currently in the postgresql-overlay/experimental.
Well, you seem to be right about the lag thing. But it feels tremendous ;-) Maybe because of the fact that 8.1 is ~ and influenced by those comments about doing things slowly. Which is, again, let me stress it, absolutely understandable. I've taken a look at experimental overlay and noticed that. But I got the feeling that in some aspects overlay is lagging and modeled it after portage version. I still think that since we have the broken slotting in portage it may make sense to put 8.2.0 in as well. Anyway, as I am willing to help, do you want me to redo it and base my work on the latest overlay version (or do you have more changes in your sleeve?)? And how soon do you expect this new stuff to go into main tree?
(In reply to comment #20) > And here comes the problem: The existing slotting is broken. There are > file-collisions between the different slots of libpq. And we're preparing a new > slotting (also for the server) which will work. This stuff is currently in the > postgresql-overlay/experimental. I've taken a closer look at experimental slotting and basically I have nearly done it. But I don't think it is a good idea, honestly. Pleases, don't take me wrong - I'm just stating my opinion (which nobody asked for). First, the amount of tweaking in code suggests that it will delay each new release and all the inevitable omissions will at best keep ebuilds in '~' for ages. And I'm pretty sure it will break all the software that is there to break. Besides, I strongly disliked the idea of changing .so major and minor numbers at will. I think it's a bit too high price for barely needed slotting. Sure, I can upload my ebuilds if you want.
Michael: You might want to read the following: http://overlays.gentoo.org/proj/postgresql/wiki/WikiStart
(In reply to comment #23) > Michael: You might want to read the following: > http://overlays.gentoo.org/proj/postgresql/wiki/WikiStart Thank you for the pointer. I see you are determined to go all the way to the advanced slotting techniques. That means I will upload my ebuilds shortly to save you some hassle preparing the patches, but surely it's just half the way. Right now I'm trying to poke you on #gentoo-db, maybe I'm still there when you're on and active (polyonymous is the nickname)
Created attachment 104326 [details] an attempt on heavily slotted ebuilds. Here they go - my attempt on both libpq and postgresql ebuilds heavily patched for slotting.
I don't believe these ebuilds have a USE flag for the new native ldap ability in PostgreSQL 8.2 --with-ldap
ok... I see that this "an attempt on heavily slotted ebuilds" fails on gentoo-patching at postgresql. If I remove regression test part of this patch - everything works ok. I will append modified version of your ebuilds soon. plz wait ;)
Created attachment 105807 [details] libpq + PostgreSQL 8.2.0 (slotting, fixed patching) fixed slotted ebuild
(In reply to comment #27) > ok... I see that this "an attempt on heavily slotted ebuilds" fails on > gentoo-patching at postgresql. If I remove regression test part of this patch - > everything works ok. I will append modified version of your ebuilds soon. plz > wait ;) It's strange that it failed for you (thanks for fixing it, anyway), but, at any rate, after I discussed all of those attempts (mine as well as theirs) with gentoo devs on IRC, it seems like neither way of slotting presented here is going to make its way into portage as is. If I were to recommend you something (although, not being gentoo developer I don't feel like I should), I'd recommend the 2nd and 3rd attachments - dev-db/libpq and dev-db/postgresql ebuilds which are modeled after current portage versions. It lacks ldap support, though, but it's easy to add. If you really need it I can submit patch too. Or wait. The really working slotting will be different from what you can see in this bug. While the tremendous lag increases what you have in this bug (ebuild attachments) is roughly what you would get if you wanted it to go into portage real fast.
Created attachment 106296 [details] libpq + postgresql 8.2.1 ebuilds (no slotting) ok. if there will not be any slotting in the portage - here is 8.2.1 version without it :)
I just added the postgresql overlays with layman. Are there going to be any 8.2 ebuilds there? I don't care about slotting -- I can de-install 8.1.5 without getting into trouble.
(In reply to comment #31) > I just added the postgresql overlays with layman. Are there going to be any 8.2 > ebuilds there? I don't care about slotting -- I can de-install 8.1.5 without > getting into trouble. > there are 8.2.0 and 8.2.1 ! can't you see? libpq + postgresql 8.2.1 ebuilds (no slotting) in attachment section ;)
Ah ... in Bugzilla I see them -- I thought they would be in one of the postgresql overlays. ls -l /usr/portage/local/layman/postgresql-experimental/dev-db/postgresql total 48 -rw-r--r-- 1 root root 14687 Jan 9 20:48 Manifest drwxr-xr-x 3 root root 4096 Jan 9 20:48 files -rw-r--r-- 1 root root 164 Jan 9 20:48 metadata.xml -rw-r--r-- 1 root root 8459 Jan 9 20:48 postgresql-8.0.8-r1.ebuild -rw-r--r-- 1 root root 9337 Jan 9 20:48 postgresql-8.1.4-r1.ebuild
PostgreSQL 8.2.1 has landed in the overlays, specifically postgresql-experimental. However, dev-db/postgresql-server-8.2.1 crashes in the emerge very quickly: # emerge -v postgresql Calculating dependencies... done! >>> Emerging (1 of 2) dev-db/postgresql-server-8.2.1 to / Traceback (most recent call last): File "/usr/bin/emerge", line 5270, in ? retval = emerge_main() File "/usr/bin/emerge", line 5265, in emerge_main myopts, myaction, myfiles, spinner) File "/usr/bin/emerge", line 4732, in action_build retval = mergetask.merge(pkglist, favorites, mtimedb) File "/usr/bin/emerge", line 2980, in merge prev_mtimes=ldpath_mtimes) File "/usr/lib/portage/pym/portage.py", line 3518, in doebuild alluris, aalist = mydbapi.getfetchlist( File "/usr/lib/portage/pym/portage.py", line 5846, in getfetchlist myurilist = portage_dep.use_reduce(myurilist,uselist=useflags,matchall=all) File "/usr/lib/portage/pym/portage_dep.py", line 213, in use_reduce raise portage_exception.InvalidDependString( portage_exception.InvalidDependString: Conditional without parenthesis: 'test?' ------------------------------------------------------------------------------- Here's the emerge info: # emerge --info Portage 2.1.2-r1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r4 i686) ================================================================= System uname: 2.6.19-gentoo-r4 i686 Pentium III (Coppermine) Gentoo Base System version 1.12.9 Timestamp of tree: Sun, 21 Jan 2007 20:30:01 +0000 dev-java/java-config: 1.3.7, 2.0.31-r3 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.19.2-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.mirrors.easynews.com/linux/gentoo/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://gentoo.mirrors.tds.net/gentoo ftp://mirror.datapipe.net/gentoo http://mirror.datapipe.net/gentoo" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/science /usr/portage/local/layman/sunrise /usr/portage/local/layman/postgresql-testing /usr/portage/local/layman/postgresql-experimental" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d a52 aac aalib activefilter ada adns agg alsa amr ansi ao aotuv apache2 apm aspell atlas auctex audiofile backtrace bash-completion bcp berkdb big-tables bitmap-fonts bjam blas bonobo boost branding bzip2 cairo cblas ccache cddb cdr cgi cli client clisp cluster cmucl cracklib crypt cscope css curl cvs dga dhcp djbfft dlloader dri dts dv dvd dvdr dvdread effects elf emacs emboss emf encode enscript exif extraengine extrafilters f90 fame fastcgi ffmpeg fftw firefox fits flac fltk foomaticdb force-reg fortran fpx fuse gcl gd gdbm geos ggi gif ginac glade glibc-omitfp glitz glut glw gmath gml gmp gnuplot gpm grammar graphviz gs gtk gtk2 gtkhtml gtkspell guile haskell hdf hlapi html icon iconv imagemagick imlib inkjar iodbc iplsrc ipv6 isdnlog ispell jack java javamail jbig jce jpeg jpeg2k jython kdeenablefinal kig-scripting kirbybase kqemu lame lapack largefile latex lcms libcaca libg++ libgda libwww lighttpd lm_sensors logitech-mouse lua lzo mad markdown math max-idx-128 mdb mfd-rewrites mikmod mjpeg mmap mmx mng mono motif mozbranding mozcalendar mozdevelop mozdom mozsha1 mozsvg mozxmlterm mp3 mp3rtp mpeg mpm-prefork musepack musicbrainz mysql ncurses netcdf new-clx nptl nptlonly nsplugin ntfs numeric nvidia objc ocaml odbc ogdi ogg openexr opengl pam pascal pcntl pcre pdf perforce perl pg-hier pg-intdatetime pg-vacuumdelay php pike plotutils plugin png portaudio posix postgres povray pppd preview-latex pulseaudio pygrub pyste python qt3 qt3support qt4 quicktime rdesktop readline reiserfs rhino ruby samba sbcl screen sdl seamonkey server session silvercity slang smux sndfile source spell spl sql sqlite sqlite3 sse sse-filters ssl subversion svg svga svgz sysfs szip t1lib tcl tcltk tcpd tetex textile theora thesaurus thumbnail tidy tiff timidity tk toolbar truetype truetype-fonts type1-fonts udev umfpack unicode usb v4l v4l2 vcd vim vim-pager vim-with-x vnc vorbis wmf wordperfect x264 x86 xml xorg xpm xrandr xscreensaver xslt xterm xv xvid yv12 zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nv" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #34) > PostgreSQL 8.2.1 has landed in the overlays, specifically > postgresql-experimental. However, dev-db/postgresql-server-8.2.1 crashes in the > emerge very quickly: Indeed, with newest portage that was the case. I think this is fixed now.
8.2.1 ebuilds compiled OK for me, please commit to portage!
yes, when will we see 8.2.1 in portage? thank you!
(In reply to comment #37) > yes, when will we see 8.2.1 in portage? thank you! config.status: creating GNUmakefile config.status: creating src/Makefile.global config.status: WARNING: src/Makefile.global.in seems to ignore the --datarootdir setting config.status: error: cannot find input file: src/include/pg_config.h.in !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/dev-db/postgresql-server-8.2.1/work/postgresql-8.2.1/config.log !!! ERROR: dev-db/postgresql-server-8.2.1 failed.
> config.status: creating GNUmakefile > config.status: creating src/Makefile.global > config.status: WARNING: src/Makefile.global.in seems to ignore the > --datarootdir setting > config.status: error: cannot find input file: src/include/pg_config.h.in Can you tell more? This message sounds like the file didn't come with your postgresql-base-8.2.1.tar.bz2 tarball, which shouldn't be the case.
> Can you tell more? This message sounds like the file didn't come with your > postgresql-base-8.2.1.tar.bz2 tarball, which shouldn't be the case. All I can say is that I got the source from the postgresql-experimental overlay revision 174 through layman today.
> All I can say is that I got the source from the postgresql-experimental overlay > revision 174 through layman today. Not much. Can you at least attach the log file and your emerge --info output?
Created attachment 108232 [details] config.log for failed server ebuild
Created attachment 108234 [details] emerge info for failed postgresql server ebuild
(In reply to comment #43) > Created an attachment (id=108234) [edit] > emerge info for failed postgresql server ebuild Thank you, pF. Unfortunately, so far I haven't been able to reproduce the failure. Maybe you can dig into the problem yourself and share some clues you find? Has anyone else experienced similar problem?
Now all of 8.2.1 has installed itself successfully during an "emerge -uDav world". I don't know why.
The new 8.2.1 installation demands that 'eselect postgresql' be run before it can 'initdb'. However, # eselect postgresql set 8.2 ~/dri-source !!! Error: /usr/include/postgresql exists and is not a symbolic link zsh: 29674 killed eselect postgresql set 8.2 # postgresql-config set 8.2 ~/dri-source !!! Error: /usr/include/postgresql exists and is not a symbolic link zsh: 29797 killed postgresql-config set 8.2 # postgresql-config list ~/dri-source Available postgresql installations 8.2 client-8.2.1 docs-8.2.1 libs-8.2.1 server-8.2.1 # eselect postgresql show ~/dri-source (none)
> !!! Error: /usr/include/postgresql exists and is not a symbolic link This is a leftover from old installation. It is yet to discover how come it isn't removed and how to deal with it. Meanwhile, check that you don't have anything of importance there and remove the directories /usr/include/postgresql/ and /usr/include/libpq/ before selecting postgresql. Thank you for report.
In an attempt to rectify this I unmerged postgresql, client, server and libpq and removed /usr/include/postgresql/ and /usr/include/libpq/; then I resynced the overlay to revision 177. The subsequent emerges of client and server now fail, though. make[4]: Entering directory `/var/tmp/portage/dev-db/postgresql-client-8.2.1/work/postgresql-8.2.1/src/backend/parser' i686-pc-linux-gnu-gcc -O2 -march=pentium2 -pipe -fomit-frame-pointer -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -I. -I/usr/include/postgresql-8.2/server -I/usr/include/postgresql-8.2/internal -D_GNU_SOURCE -c -o keywords.o keywords.c -MMD -MP -MF .deps/keywords.Po distcc[30406] ERROR: compile (null) on localhost failed common.c:19:25: error: postgres_fe.h: No such file or directory In file included from pg_backup.h:28, from pg_backup_archiver.h:32, from common.c:20: pg_dump.h:38: error: expected specifier-qualifier-list before ‘Oid’ distcc[30416] ERROR: compile (null) on localhost failed pg_dump.h:53: error: expected specifier-qualifier-list before ‘Oid’ pg_dump.h:122: error: expected specifier-qualifier-list before ‘bool’ pg_dump.h:144: error: expected specifier-qualifier-list before ‘Oid’ pg_dump.h:168: error: expected specifier-qualifier-list before ‘Oid’ pg_dump.h:186: error: expected specifier-qualifier-list before ‘Oid’ pg_dump.h:212: error: expected specifier-qualifier-list before ‘bool’ pg_dump.h:262: error: expected specifier-qualifier-list before ‘bool’ ... -------------------------------------------------------------- ... make[2]: Entering directory `/var/tmp/portage/dev-db/postgresql-server-8.2.1/work/postgresql-8.2.1/src/port' i686-pc-linux-gnu-gcc -O2 -march=pentium2 -pipe -fomit-frame-pointer -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -I../../src/port -I/usr/include/postgresql-8.2/server -I/usr/include/postgresql-8.2/internal -D_GNU_SOURCE -c strlcpy.c -o strlcpy_srv.o distcc[4660] ERROR: compile (null) on localhost failed strlcpy.c:35:15: error: c.h: No such file or directory strlcpy.c:45: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘strlcpy’ distcc[4659] ERROR: compile strlcpy.c on localhost failed make[2]: *** [strlcpy_srv.o] Error 1 ...
Created attachment 108829 [details] Client Rev. 177 Failed Emerge Log.
Created attachment 108831 [details] Server Rev. 177 Failed Emerge Log.
(In reply to comment #48) > In an attempt to rectify this I unmerged postgresql, client, server and libpq > and removed /usr/include/postgresql/ and /usr/include/libpq/; then I resynced > the overlay to revision 177. > > The subsequent emerges of client and server now fail, though. It does look like you don't have postgresql-libs properly installed. Do you have files in /usr/include/postgresql-8.2/ ? > i686-pc-linux-gnu-gcc -O2 -march=pentium2 -pipe -fomit-frame-pointer -Wall > -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement > -Wendif-labels -fno-strict-aliasing -I. -I/usr/include/postgresql-8.2/server > -I/usr/include/postgresql-8.2/internal -D_GNU_SOURCE -c -o keywords.o > keywords.c -MMD -MP -MF .deps/keywords.Po > distcc[30406] ERROR: compile (null) on localhost failed > common.c:19:25: error: postgres_fe.h: No such file or directory In particular do you have /usr/include/postgresql-8.2/server/postgres_fe.h ? You should... I'll try upgrading postgresql on yet another server today and see if it works... I'm happy to have you as a tester, since you seem to reveal all possible and impossible bugs ;-)
(In reply to comment #51) > It does look like you don't have postgresql-libs properly installed. Do you have files in /usr/include/postgresql-8.2/ ? No! That was probably the problem. I'm currently running a re-emerge of libs, client, server, meta and pq from scratch having removed the include directories. One other question: is the lack of an emerge --config just temporary? (I don't want to use it - based on past experience - because I want UTF8 as the default encoding.)
The emerge proceeded as follows, after starting with NO postgresql-related directories in /usr/include: pq succeeds, then libs fails with the 'leftover' message. ---------------------------------------------------------- emerge -av libpq postgresql These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-db/libpq-8.1.5 USE="nls pam readline ssl zlib -kerberos -pg-intdatetime -threads" 7,998 kB [ebuild N ] dev-db/postgresql-libs-8.2.1 USE="ldap nls pam readline ssl zlib -eselect -kerberos -pg-intdatetime -threads" LINGUAS="-af -cs -de -es -fa -fr -hr -hu -it -ko -nb -pl -pt_BR -ro -ru -sk -sl -sv -tr -zh_CN -zh_TW" 8,285 kB [8] [ebuild N ] dev-db/postgresql-client-8.2.1 164 kB [8] [ebuild N ] dev-db/postgresql-server-8.2.1 USE="perl python xml (-selinux) -tcl -test" 0 kB [8] [ebuild N ] dev-db/postgresql-8.2.1 USE="client doc server" 0 kB [8] [...] >>> Emerging (2 of 5) dev-db/postgresql-libs-8.2.1 to / * postgresql-base-8.2.1.tar.bz2 MD5 ;-) ... [ ok ] * postgresql-base-8.2.1.tar.bz2 RMD160 ;-) ... [ ok ] * postgresql-base-8.2.1.tar.bz2 SHA1 ;-) ... [ ok ] * postgresql-base-8.2.1.tar.bz2 SHA256 ;-) ... [ ok ] * postgresql-base-8.2.1.tar.bz2 size ;-) ... [ ok ] >>> Creating Manifest for /usr/portage/local/layman/postgresql-experimental/dev-db/postgresql-libs digest.assumed 7 digest-postgresql-libs-7.3.17::postgresql-base-7.3.17.tar.bz2 digest-postgresql-libs-7.4.15::postgresql-base-7.4.15.tar.bz2 digest-postgresql-libs-8.0.10::postgresql-base-8.0.10.tar.bz2 digest-postgresql-libs-8.0.10::postgresql-opt-8.0.10.tar.bz2 digest-postgresql-libs-8.1.6::postgresql-base-8.1.6.tar.bz2 digest-postgresql-libs-8.1.6::postgresql-opt-8.1.6.tar.bz2 digest-postgresql-libs-8.2.1::postgresql-test-8.2.1.tar.bz2 * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking postgresql-base-8.2.1.tar.bz2 ;-) ... [ ok ] * You have leftovers from previous installations that can't be * dealt with automatically. The proper way to treat files is: * * rm -rf //usr/include/postgresql * !!! ERROR: dev-db/postgresql-libs-8.2.1 failed. !!! Please, remove the files manually ---------------------------------------------------------- After the failed emerge attempt the directory is there. ---------------------------------------------------------- valli ~ # ls -l /usr/include/postgresql ~ total 4 drwxr-xr-x 3 root root 8 Feb 1 12:00 internal drwxr-xr-x 2 root root 3 Feb 1 12:00 libpq drwxr-xr-x 5 root root 10 Feb 1 12:00 libpq-4 lrwxrwxrwx 1 root root 42 Feb 1 12:00 libpq-fe.h -> /usr/include/postgresql/libpq-4/libpq-fe.h lrwxrwxrwx 1 root root 43 Feb 1 12:00 pg_config.h -> /usr/include/postgresql/libpq-4/pg_config.h lrwxrwxrwx 1 root root 50 Feb 1 12:00 pg_config_manual.h -> /usr/include/postgresql/libpq-4/pg_config_manual.h lrwxrwxrwx 1 root root 46 Feb 1 12:00 pg_config_os.h -> /usr/include/postgresql/libpq-4/pg_config_os.h lrwxrwxrwx 1 root root 46 Feb 1 12:00 postgres_ext.h -> /usr/include/postgresql/libpq-4/postgres_ext.h drwxr-xr-x 19 root root 37 Feb 1 12:00 server ---------------------------------------------------------
> emerge -av libpq postgresql Okay, I see the problem now. I was postponing adding blocker for libpq. You should not install libpq as it is superceeded by postgresql-libs. I've just updated ebuilds to add blocker for libpq. You should only install postgresql-* ebuilds (or postgresql meta-ebuild with properly set use flags). Note, that this is highly experimental stuff and it's not yet consistent with the rest of the tree, so to get dependent packages from tree build against the postgresq you'll have to add libpq to package.provided. Here is, for instance, mine: tartaros postgresql-libs # cat /etc/portage/profile/package.provided dev-db/libpq-8.2.0 tartaros postgresql-libs # And then, after eselecting postgres, you can build packages that depend on postgresql (e.g. php with postgres USE, libpqxx, etc.)
> One other question: is the lack of an emerge --config just temporary? (I don't > want to use it - based on past experience - because I want UTF8 as the default > encoding.) No, there's no lack of emerge --config. It's just that it's been moved to postgresql-server. I understand there's a better configurator for postgresql in the works which should also let you to set various parameters interactively. At the moment I can't tell you much about it, as I'm not really involved with it (yet?:)). But, I'm using utf8 myself and this is how: env LC_CTYPE=en_US.utf8 LC_COLLATE=en_US.utf8 emerge --config ....
Thank you Michael: almost total success except for running eselect after the 'emerge --config postgresql-server'. valli dri-source # eselect postgresql list Available postgresql installations 8.2 client-8.2.1 docs-8.2.1 libs-8.2.1 server-8.2.1 valli dri-source # eselect postgresql set 8.2 /usr/share/eselect//modules/postgresql.eselect: line 92: /etc/eselect/postgresql/active.links: No such file or directory !!! Error: Failed to store list of links Call stack: * do_set (postgresql.eselect:92) * check_do (core.bash:26) * do_action (core.bash:95) * main (eselect:190) zsh: 19852 killed eselect postgresql set 8.2 valli dri-source # eselect postgresql show (none)
(In reply to comment #56) > Thank you Michael: almost total success except for running eselect after the > 'emerge --config postgresql-server'. Aha, we're nearly there... > valli dri-source # eselect postgresql list > Available postgresql installations > 8.2 client-8.2.1 docs-8.2.1 libs-8.2.1 server-8.2.1 > valli dri-source # eselect postgresql set 8.2 > /usr/share/eselect//modules/postgresql.eselect: line 92: > /etc/eselect/postgresql/active.links: No such file or directory Weird. Do you have /etc/eselect/postgresql directory? What is your bash --version?
valli ~ # ls -alrt /etc/eselect ~ total 17 drwxr-xr-x 2 root root 6 2006-09-01 11:25 compiler -rw-r--r-- 1 root root 2261 2007-01-09 05:23 ld-mtimedb drwxr-xr-x 3 root root 4 2007-01-31 05:03 . drwxr-xr-x 99 root root 270 2007-02-03 03:57 .. ------------------------------------------------------- valli ~ # ls -lart /etc/eselect/postgresql ~ ls: cannot access /etc/eselect/postgresql: No such file or directory ------------------------------------------------------- valli ~ # bash --version ~ GNU bash, version 3.2.9(1)-release (i686-pc-linux-gnu) Copyright (C) 2005 Fvalli ~ # eix -v postgresql ~ ------------------------------------------------------- (Note typo 'psotgresql' in this description from eix: * app-admin/eselect-postgresql [2] Available versions: (~)0 Installed versions: Version: 0 Date: 05:03:37 AM 01/31/2007 Best versions/slot: (~)0 Homepage: http://www.gentoo.org/ Description: Utility to change the default psotgresql installation License: GPL-2 ree Software Foundation, Inc.) ------------------------------------------------------- revdep-rebuild errors after removing libpq ------------------------------------------------------- valli ~ # revdep-rebuild ~ Configuring search environment for revdep-rebuild Checking reverse dependencies... Packages containing binaries and libraries broken by a package update will be emerged. Collecting system binaries and libraries... done. (/root/.revdep-rebuild.1_files) Collecting complete LD_LIBRARY_PATH... done. (/root/.revdep-rebuild.2_ldpath) Checking dynamic linking consistency... broken /usr/bin/b2m-xemacs (requires libpq.so.4) broken /usr/bin/ctags-xemacs (requires libpq.so.4) broken /usr/bin/ellcc (requires libpq.so.4) broken /usr/bin/etags-xemacs (requires libpq.so.4) broken /usr/bin/gnuclient (requires libpq.so.4) broken /usr/bin/ootags (requires libpq.so.4) broken /usr/bin/xemacs-21.4.20 (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/cvtmail (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/digest-doc (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/fakemail (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/gnuserv (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/hexl (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/make-docfile (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/mmencode (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/movemail (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/profile (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/sorted-doc (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/wakeup (requires libpq.so.4) broken /usr/lib/xemacs-21.4.20/i686-pc-linux/yow (requires libpq.so.4) done. (/root/.revdep-rebuild.3_rebuild) Assigning files to ebuilds... done. (/root/.revdep-rebuild.4_ebuilds) Evaluating package order... done. (/root/.revdep-rebuild.5_order) All prepared. Starting rebuild... emerge --oneshot =app-editors/xemacs-21.4.20-r1 [...] ..........checking for postgresql/libpq-fe.h... no Error: Required PostgreSQL support cannot be provided. Check --site-prefixes. !!! ERROR: app-editors/xemacs-21.4.20-r1 failed. [...] ---------------------------------------------------------- valli ~ # < /etc/portage/profile/package.provided ~ dev-db/libpq-8.2.0
(In reply to comment #58) > valli ~ # ls -lart /etc/eselect/postgresql > ~ > ls: cannot access /etc/eselect/postgresql: No such file or directory Ah, thank you, I see the problem now. I've updated app-admin/eselect-postgresql ebuild. Try updating overlay and re-emerging it. And then 'eselect postgresql set 8.2'. > (Note typo 'psotgresql' in this description from eix: Thanks! > revdep-rebuild errors after removing libpq This is normal. libpq is now provided by postgresql-libs. So, once you have package.provided, just run revdep-rebuild or re-emerge packages in question yourself, whichever you prefer. It is normal that your rebuild failed without eselecting postgresql first. I do not use emacs and lots of other packages that you have that depend on postgresql, so I haven't tested them. If any of those fail, your feedback is much appreciated.
> broken /usr/bin/b2m-xemacs (requires libpq.so.4) And, btw, you have one more option fixing these inconsistencies: you can install postgresql 8.1 slot which provides libpq.so.4
Everything 8.2.1 now installs and configures properly, and new packages - eg amarok - build with postgresql 8.2.1 support. Xemacs rebuilt correctly. (I did not use an 8.1 slot.)
> Everything 8.2.1 now installs and configures properly, and new packages - eg > amarok - build with postgresql 8.2.1 support. Xemacs rebuilt correctly. (I > did not use an 8.1 slot.) Thank you. That's good to know.
Created attachment 109939 [details] qt build fails w/r/t postgresql 8.2.3 peter@valli ~ % sudo emerge -1pv qt These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-libs/qt-4.2.2 USE="cups dbus gif glib* jpeg opengl pch* png postgres* qt3support zlib -accessibility -debug -doc -examples -firebird -mng -mysql* -nas -nis -odbc -sqlite -sqlite3 -xinerama" INPUT_DEVICES="-wacom" 0 kB [...] PostgreSQL auto-detection... () g++ -c -pipe -O2 -march=pentium2 -pipe -Wall -W -I../../../mkspecs/linux-g++ -I. -IUse -I/usr/include/postgresql/pgsql -I. -o psql.o psql.cpp psql.cpp:1:22: error: libpq-fe.h: No such file or directory psql.cpp: In function ‘int main(int, char**)’: psql.cpp:5: error: ‘PQescapeBytea’ was not declared in this scope psql.cpp:6: error: ‘PQunescapeBytea’ was not declared in this scope make: *** [psql.o] Error 1 PostgreSQL disabled. PostgreSQL support cannot be enabled due to functionality tests! Turn on verbose messaging (-v) to ./configure to see the final report. If you believe this message is in error you may use the continue switch (-continue) to ./configure to continue. !!! ERROR: x11-libs/qt-4.2.2 failed.
(In reply to comment #63) I'm downloading this qt version now, but this is weirdness: > PostgreSQL auto-detection... () > g++ -c -pipe -O2 -march=pentium2 -pipe -Wall -W -I../../../mkspecs/linux-g++ > -I. -IUse -I/usr/include/postgresql/pgsql -I. -o psql.o psql.cpp > psql.cpp:1:22: error: libpq-fe.h: No such file or directory libpq-fe.h has never been /usr/include/postgresql/pgsql, I don't know why it looks for it there. Well, more to follow.
(In reply to comment #63) > Created an attachment (id=109939) [edit] > qt build fails w/r/t postgresql 8.2.3 Hmm... PostgreSQL auto-detection... () g++ -c -pipe -O2 -pipe -march=athlon-xp -Wall -W -I../../../mkspecs/linux-g++ -I. -I/usr/include/postgresql-8.2 -I/usr/include/mysql -I/usr/include/postgresql/pgsql -I. -o psql. o psql.cpp g++ -o psql psql.o -L/usr/lib/postgresql-8.2/lib -L/usr/lib/mysql -lpq PostgreSQL enabled. Do you have postgresql eselected, anyway? Can you pg_config --version ?
(In reply to comment #65) > Do you have postgresql eselected, anyway? Can you pg_config --version ? > Strangely, I found it to be unselected; I didn't manually do that. I'll try the build again. valli ~ # eselect postgresql show (none) valli ~ # eselect postgresql list Available postgresql installations 8.2 client-8.2.3 docs-8.2.3 libs-8.2.3 server-8.2.3 valli ~ # eselect postgresql set 8.2 valli ~ # pg_config --version PostgreSQL 8.2.3
(In reply to comment #66) Thank you Michael, the build succeeded. It must have been due to postgresql's being de-eselected. I can only surmise that the upgrades from 8.2.1 did that.
(In reply to comment #67) > (In reply to comment #66) > Thank you Michael, the build succeeded. It must have been due to postgresql's > being de-eselected. I can only surmise that the upgrades from 8.2.1 did that. Well, the cause could be somewhere in ebuilds, since the experimental overlay changes somewhat inconsistently as there are no explicit revision bumps.
(In reply to comment #68) Michael, any idea where that erroneous path /usr/include/postgresql/pgsql originated? peter@valli ~ % ls -alrt `locate libpq-fe.h` -rw-r--r-- 1 root root 17983 2007-02-12 09:13 /usr/include/postgresql-8.2/libpq-fe.h lrwxrwxrwx 1 root root 38 2007-02-12 11:40 /usr/include/libpq-fe.h -> /usr/include/postgresql-8.2/libpq-fe.h peter@valli ~ % ls -alrt /usr/include/postgresql/pgsql ls: cannot access /usr/include/postgresql/pgsql: No such file or directory
(In reply to comment #69) > Michael, any idea where that erroneous path /usr/include/postgresql/pgsql > originated? I haven't given it much thought, but the first guess would be that it is some hardcoded fallback in qt build system. I take it, when you do have eselected slot it doesn't look there for libpq-fe.h, right?
(In reply to comment #70) >I take it, when you do have eselected > slot it doesn't look there for libpq-fe.h, right? No, the build proceeded straight through without problems. I'm not sure whether that directory was still redundantly within the include path somewhere though.
(In reply to comment #71) > No, the build proceeded straight through without problems. I'm not sure > whether that directory was still redundantly within the include path somewhere > though. I think you need not worry.
Using 8.2.1 ebuild I noticed pg_config is not showing some variable properly Wrong: SHAREDIR = /usr/share/postgresql PGXS = /usr/lib64/postgresql/pgxs/src/makefiles/pgxs.mk Right: SHAREDIR = /usr/share/postgresql-8.2 PGXS = /usr/lib64/postgresql-8.2/pgxs/src/makefiles/pgxs.mk Also, is following correct ? SYSCONFDIR = /etc/postgresql
How close is this to being done? Any hope to see 8.2.3 in portage? any time frame estimates at all? Thank you very much.
(In reply to comment #73) > Using 8.2.1 ebuild I noticed pg_config is not showing some variable properly Yogesh, sorry, I haven't seen this comment before. What ebuilds are you referring to? The ebuilds in works are in postgresql overlay. And their pg_configs seem to provide correct information.
*** Bug 171077 has been marked as a duplicate of this bug. ***
hi all in this bug, I'm former postgresql maintener in gentoo. If no active person is in postgreqsl herd, I'll join it again. What do you think?
no.
ok, i just understood the current situation in irc. i'll leave it.
(In reply to comment #79) > ok, i just understood the current situation in irc. i'll leave it. This means we have to wait for a year to see 8.2 in portage?
ALso asking about the timeframes expected for 8.2 to make it into portage. Perhaps get a 8.2.3 for those running non qt servers and <8.2.3 for the qt desktops? /me needs to deploy a few postgresql servers and would've prefered to have them "standard" gentoo with postgresql
(In reply to comment #81) > ALso asking about the timeframes expected for 8.2 to make it into portage. > Perhaps get a 8.2.3 for those running non qt servers and <8.2.3 for the qt > desktops? I don't think I'm entitled to say anything on expected timeframes, but what does this version limitation have to do with (or better have to oppose) qt? To the best of my knowledge overlay ebuilds coexist with qt peacefully and nicely. > /me needs to deploy a few postgresql servers and would've prefered to have them > "standard" gentoo with postgresql Similar attitude had significant influence on my decision to proceed with working on these ebuilds: I wanted to install ebuilds that resemble future portage versions as closely as possible. So, I _hope_ the experimental overlay version serve this purpose, but it is experimental nonetheless.
*** Bug 172670 has been marked as a duplicate of this bug. ***
*** Bug 172654 has been marked as a duplicate of this bug. ***
Created attachment 114868 [details] libpq-8.2.3++postgresql-8.2.3.tar.bz2 ebuilds with patches and files for version 8.2.3 of dev-db/libpq and dev-db/postgresql
> Created an attachment (id=114868) [edit] > libpq-8.2.3++postgresql-8.2.3.tar.bz2 > > ebuilds with patches and files for version 8.2.3 of dev-db/libpq and > dev-db/postgresql Sascha, I'd recommend that you read this bug first - it may be very entertaining and educating, if you're interested in postgresql and gentoo relationships. In short, the new ebuilds in works are in overlay and they differ from the current portage version a lot.
(In reply to comment #86) > Sascha, I'd recommend that you read this bug first - it may be very > entertaining and educating, if you're interested in postgresql and gentoo > relationships. In short, the new ebuilds in works are in overlay and they > differ from the current portage version a lot. > I needed a quick way to get this postgresql version in my portage. I had to migrate a database to a gentoo system, so i recoded the ebuilds from earlier versions and they work good now. I just wanted to help you guys. Its up to you, you can throw it in the trashcan, if its not working for gentoo. ;) cheers, yours, Sascha
> > I needed a quick way to get this postgresql version in my portage. > I had to migrate a database to a gentoo system, so i recoded the ebuilds from > earlier versions and they work good now. > > I just wanted to help you guys. Its up to you, you can throw it in the > trashcan, if its not working for gentoo. ;) Thank you, I didn't exactly mean to discourage you, sorry if it came out that way.
(In reply to comment #88) > > > > I needed a quick way to get this postgresql version in my portage. > > I had to migrate a database to a gentoo system, so i recoded the ebuilds from > > earlier versions and they work good now. > > > > I just wanted to help you guys. Its up to you, you can throw it in the > > trashcan, if its not working for gentoo. ;) > > Thank you, I didn't exactly mean to discourage you, sorry if it came out that > way. > Not to beat a dead horse ... but ... any idea on an ETA?
Ebuild from the experimental overlay work fine here on x86 (P4 Prescott). I am able to load my data from a pg_dumpall of my 8.1 server as well. No issues here.
This is not working :( checking for sgmlspl... no checking thread safety of required library functions... no configure: error: thread test program failed This platform is not thread-safe. Check the file 'config.log'for the exact reason. You can use the configure option --enable-thread-safety-force to force threads to be enabled. But you must then run the program in src/test/thread and add locking function calls to your applications to guarantee thread safety. !!! ERROR: dev-db/libpq-8.2.3 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 3401: Called src_compile libpq-8.2.3.ebuild, line 71: Called die !!! configure failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-db/libpq-8.2.3/temp/build.log'. !!! This ebuild is from an overlay: '/home/fsousa/portage' $ emerge --info Portage 2.1.2.2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.5-r0, 2.6.19-gentoo-r5 x86_64) ================================================================= System uname: 2.6.19-gentoo-r5 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz Gentoo Base System release 1.12.9 Timestamp of tree: Sat, 14 Apr 2007 08:30:01 +0000 dev-java/java-config: 1.3.7, 2.0.31-r5 dev-lang/python: 2.4.4, 2.5-r2 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.15-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -msse3 -O2 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=nocona -msse3 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages metadata-transfer paralell-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://darkstar.ist.utl.pt/gentoo/" LANG="pt_PT@euro" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/fsousa/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="7zip X acpi alsa amd64 apache2 arts bash-completion berkdb bitmap-fonts bzip2 cli cracklib crypt cups dbus dri emacs firefox fontconfig gdbm hal iconv isdnlog jpeg kdehiddenvisibility libg++ midi mp3 mysql ncurses newspr nls nptl nptlonly nsplugin nvidia ogg opengl pam pch pcre pdf perl png postgres ppds pppd python readline reflection sdl session smp spl ssl svg syslog tcpd threads truetype truetype-fonts type1-fonts usb vorbis xinerama xorg xscreensaver zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nv" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Hey Filipe, On SMP systems try -> USE="-threads" for libpq-8.2.3 Should be fixed, i know... :[ CAUTION: This will lead to only one CPU being used by a postgresql instance. Very disturbing in productive environments with more than one CPU.
(In reply to comment #92) > Hey Filipe, > > On SMP systems try -> USE="-threads" for libpq-8.2.3 > Should be fixed, i know... :[ I think it's pretty random bug in test and it goes away sometimes when you just rerun emerge. Well, I think this needs more attention, anyway. > CAUTION: This will lead to only one CPU being used by a postgresql instance. > Very disturbing in productive environments with more than one CPU. The thread safety doesn't affect postgresql in any way, it only affects client libraries.
8.2.4 is out and stable now...
(In reply to comment #94) > 8.2.4 is out and stable now... > Thanks... I think it will be in overlay in a couple of days or maybe even later today...
old-style 8.2.4 committed.
Thanks for adding 8.2.4 - I tried and it fails for me with USE="-test": >>> Unpacking postgresql-docs-8.2.4.tar.bz2 to /home/tmp/portage/dev-db/postgresql-8.2.4/work * Applying postgresql-8.2.4-gentoo.patch ... [ ok ] * Applying postgresql-8.2.4-sh.patch ... [ ok ] * Applying postgresql-8.2.4-no-test.patch ... * Failed Patch: postgresql-8.2.4-no-test.patch ! * ( /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ) * * Include in your bugreport the contents of: * * /home/tmp/portage/dev-db/postgresql-8.2.4/temp/postgresql-8.2.4-no-test.patch-8029.out When I USE="test" emerge ... it proceeds and starts autoconf etc. ***** postgresql-8.2.4-no-test.patch ***** ========================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ========================================== can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/src/Makefile b/src/Makefile |index 5eb7c4a..0f9fff0 100644 |--- a/src/Makefile |+++ b/src/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ========================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ========================================== patching file src/Makefile Hunk #1 FAILED at 22. 1 out of 1 hunk FAILED -- saving rejects to file src/Makefile.rej ========================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ========================================== patching file Makefile Hunk #1 FAILED at 22. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej ========================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ========================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/src/Makefile b/src/Makefile |index 5eb7c4a..0f9fff0 100644 |--- a/src/Makefile |+++ b/src/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ========================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-db/postgresql/files/postgresql-8.2.4-no-test.patch ========================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/src/Makefile b/src/Makefile |index 5eb7c4a..0f9fff0 100644 |--- a/src/Makefile |+++ b/src/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored $epm -q diffutils patch diffutils-2.8.7-r1 patch-2.5.9-r1 Never had any other problems with these. Any ideas?
Just for the record: 8.2.4-r1 via bug #176743 fixed my problem. Thanks!
