Re: yum repo, pgloader

On 7/22/2016 5:50 PM, Adrian Klaver wrote:
>
> If I where to hazard a guess it would have to do with pgloader
> migrating from being written in Python to being written in Common
> Lisp, that occurred at roughly the same time.

ah, yer right, the one in the pg 9.2 repo is 2.3.x, and indeed, pgloader
v2 was python.

https://github.com/dimitri/pgloader/tree/pgloader-v2

I've spent all day trying to build the lisp code on centos 6 with a lot
of frustration.   last time I even sniffed around the edges of lisp was
in the 1970s.   I've successfully built sbcl 1.3, and it passes its self
test.    building pgloader, I'm  currently stuck at...

[package pgloader]................................
..................................................
..................................................
.........;
; caught ERROR:
;   READ error during COMPILE-FILE:
;
;     Symbol "*IXF-STREAM*" not found in the IXF package.
;
;       Line: 70, Column: 25, File-Position: 2414
;
;       Stream: #<SB-INT:FORM-TRACKING-STREAM for "file /home/piercej/pgloader-3.2.2/src/sources/ixf/ixf-schema.lisp"
{1006D2FDD3}>

debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread
#<THREAD "main thread" RUNNING {1002916D53}>:
   COMPILE-FILE-ERROR while
   compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema">

Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
   0: [RETRY                        ] Retry
                                      compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema">.
   1: [ACCEPT                       ] Continue, treating
                                      compiling #<CL-SOURCE-FILE "pgloader" "src" "sources" "ixf" "ixf-schema">
                                      as having been successful.
   2:                                 Retry ASDF operation.
   3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
                                      configuration.
   4: [ABORT                        ] Give up on "pgloader"
   5: [CONTINUE                     ] Ignore runtime option --eval "(ql:quickload \"pgloader\")".
   6:                                 Skip rest of --eval and --load options.
   7:                                 Skip to toplevel READ/EVAL/PRINT loop.
   8: [EXIT                         ] Exit SBCL (calling #'EXIT, killing the process).

(UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > .
#<ASDF/LISP-ACTION:CL-SOURCE-FILE"pgloader" "src" "sources" "ixf" "ixf-schema">))) 
0]


and have no idea how to proceed.     btw,  `make` processes that go and
download huge chunks of code from 3rd party sites scare the bejeezzus
out of me.

maybe I'll dig out the v2 python code and try it.   it should be a lot
easier to deploy in our overseas manufacturing production data centers,
anyways.


--
john r pierce, recycling bits in santa cruz