Re: [Dspace-tech] Help needed with DBD::Pg
yum install perl-DBD-Pg.x86_64 worked fine for me. Really you shouldn't be building it by hand unless you have specific requirements about the build, or it isn't supported by your package manager. Jim On Mon, Jun 04, 2007 at 01:51:45PM +0930, Steve Thomas wrote: Hi. I'm wondering if anyone has installed the DBD::Pg perl module on RedHat? (RHEL) I'm having severe problems trying to get it to build. I have PostgreSQL 8.2.4 installed from a package. The DBD::Pg install requires pg_config from the development kit, so I've unpacked that and ran gmake to build pg_config. But I still cannot get the make for DBD::Pg to run - it crashes immediately with this: $ make gcc -c -I/home/uals/kit/postgresql-8.2.4/src/include -I/usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/auto/DBI -D_REENTRANT -D_GNU_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe -I/home/uals/kit/postgresql-8.2.4/src/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -DPGLIBVERSION=80204 -DPGDEFPORT=5432 -O2 -g -pipe -m64 -DPERL_EXTMALLOC_DEF -Dmalloc=Perl_malloc -Dfree=Perl_mfree -Drealloc=Perl_realloc -Dcalloc=Perl_calloc -DVERSION=\1.49\ -DXS_VERSION=\1.49\ -fPIC -I/usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE Pg.c In file included from Pg.xs:14: Pg.h:21:22: libpq-fe.h: No such file or directory In file included from Pg.h:47, from Pg.xs:14: dbdimp.h:36: error: syntax error before PGconn dbdimp.h:36: warning: no semicolon at end of struct or union etc. for about another hundred error lines. (This was after I tinkered with the DBD::Pg Makefile to adjust the erroneous paths provided by pg_config! Which made no difference.) I am afraid that at this point I am stumped. Any clues as to what to try next will be warmly welcomed. Steve Stephen Thomas, Senior Systems Analyst, University of Adelaide Library UNIVERSITY OF ADELAIDE SA 5005 AUSTRALIA Phone: +61 8 830 35190 Fax: +61 8 830 34369 Email: [EMAIL PROTECTED] URL: http://www.adelaide.edu.au/directory/stephen.thomas CRICOS Provider Number 00123M --- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as HP CONFIDENTIAL. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] [Dspace-general] DSpace: digital archive or literature archive?
MacKenzie It was not my intention to create a vendor tone around DSpace; for what its worth I have had (and seen others having) similar kinds of discussions around other OSS on other mailing lists ... with no adverse reactions. My intention was not to try and highlight any shortcomings or cast any aspersions on the usability of DSpace; rather, I was trying to see where it could or might not meet our specific needs. We do have a preference to use an OSS solution - and one of the great aspects of the OSS development model is that there is often are choices; with each one having its own pros or cons. I have already learnt a lot on this thread to help me with that choice. I also wish you well in your endeavours to continue with DSpace development - as you say, there have been inputs from the members of the DSpace technical community ... but don't forget to hear the occasional voices of the less technical as well! Derek MacKenzie Smith [EMAIL PROTECTED] 2007/06/04 03:30 PM Dear Derek, Richard, et al. I am occasionally amazed at the degree to which DSpace, after 5 years as an open source software project, is still talked about as if it were a vendor product... of course it has limitations... all software does, especially when it's five years old and actually getting used. But in this the outcome is in *your* hands. Based on its cumulative experience, last year some members of the DSpace technical community produced an architecture for needed improvements to the system: http://wiki.dspace.org/index.php/ArchReviewReport Michele Kimpton, the new Executive Director of the DSpace Foundation, is now at work on how we can collectively move that forward. We need to figure out the funding model to get this work done, but I'm pretty confident it will happen... there are too many organizations depending on DSpace now to let it age out of existence, mine included. And there's always that data export exit strategy if it does -- one of the original requirements of the system that acknowledges how short the life span of software is these days, and how little we still know about the right way to build these systems. Cheers, MacKenzie MIT Libraries Derek Hohls wrote: Richard Thanks for sharing those ideas and thoughts. I looked at the Nuxeo site, and also read through the technical comparison by Richard Wyles - very interesting. I also looked the Fedora case study implementation by Richard Green [sidebar - there do seem to be lots of Richards here... is it just a coincidence that my middle name is - Richard!] In summary, I have gathered that: * DSpace is less technically capable, does not scale as well, does not handle complex objects or variety of objects, or mass-uploading of data, but has an easy and simple front-end for users and administrators. There is also a wealth of start-up material and a good community. * Fedora is more technically capable, scales well (within our likely limits at least), seems to handle complex objects with a variety of data types - MIME- based. There is no front-end that works on the web; and the Java interface that is supplied looks absolutely barebones at best. The concepts and ideas of Fedora also seem quite complex and are not clearly explained in the starting documentation. User docs and tutorials seem minimal. Community support is unknown. Richard Green's case study says: Fedora 'out of the box' was a software tool with an associated very steep learning curve and a user had to rely heavily on documentation available on the Fedora website... we came to realise that the documentation appeared to lack some crucial elements and that, for a first time user, it was sometimes not easy to follow. * Nuxeo might be promising; it has lots of flash but the capabilities are harder to discern. The emphasis seems to be on CMS, which is not really what we need; from their website list of features: # Workspaces to create and work on documents # Flexible versioning of documents # Document Life Cycle Management # Collaboration features such as comments, on-demand notifications, etc. # Search / Query interface to the document repository This leaves us in a difficult position between two choices; (a) to hold off and hope for Fedora to significantly improve the front end and user documentation... which might be problematic as its not clear how there funding will continue after September this year (2007), and there is no project roadmap, so its not that clear as to what they will actually focus on. (b) to go on with DSpace, and acknowledge that its a temporary solution which may not adequately address many of our use cases (although still a step up from holding all research data on local drives or on a DMS). if we later decide to switch to Fedora, I hope it would be possible to extract the content out for the new system. DSpace says:
Re: [Dspace-tech] Help needed with DBD::Pg
On Mon, 2007-06-04 at 13:51 +0930, Steve Thomas wrote: I have PostgreSQL 8.2.4 installed from a package. The DBD::Pg install requires pg_config from the development kit, so I've unpacked that and ran gmake to build pg_config. But I still cannot get the make for DBD::Pg to run - it crashes immediately with this: $ make [...] Pg.h:21:22: libpq-fe.h: No such file or directory In file included from Pg.h:47, from Pg.xs:14: dbdimp.h:36: error: syntax error before PGconn dbdimp.h:36: warning: no semicolon at end of struct or union etc. for about another hundred error lines. (This was after I tinkered with the DBD::Pg Makefile to adjust the erroneous paths provided by pg_config! Which made no difference.) The libpq-fe.h file that gcc is unable to find while attempting to compile the code is the primary header file of the postqres C client development library. It defines the PGconn and other API datastructures. It's been many years since I've used RedHat with postgres. But, as I recall there was a postgres-devel package or something similar that would install this header file along with the libpq shared library. You may want to check and make sure that you have all of the postgres devel packages installed. A missing devel package and a lack of a correct devel package dependency in the perl module package would explain why this would work for some people and not others. If there is no longer a devel package, or you already have it installed, you can use 'locate' to find the libpq-fe.h header file. Then, you can either pass the appropriate arugment to './configure' to include that include file path in the include paths or, if that is not possible, edit the make file to include the path of its location after a '-I' argument to gcc. As far as I can remember, I think RedHat used to install these files in strange places like a directories called postgres in /usr/include and /usr/lib rather than those directories themselves. So, you should also be able to fix your problem by symlinking, or moving, those files into the UNIX standard directories for their file type. Although, that type of action would make it more difficult to maintain your install over time as you performed postgres upgrades. Therefor, it would be best to attempt to resolve your issue, as James suggests - by relying on the distributions packages. Reinstalling the packages can sometimes clear up the types of problems you're seeing, especially if the source code and configurations of those packages have been modified. I hope my explanation of what I believe the problem to be has made it easier for you to figure out how to correct it. - VAB signature.asc Description: This is a digitally signed message part - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] error message while opening pdf documents
Hi! In my DSpace repository, when I click the view/open option (in the Files in this Item section) to open a pdf file, it gives an error message - There was an error opening the document. The file doesn't exist. The same file opens when it is saved to the drive. Is this related with memory or adobe pdf issue? Any one had the same problem please suggest. Thanks, jayan - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
