Thread

  1. Alpha FreeBSD port of PostgreSQL !!!

    nathan@khmere.com — 2000-11-03T23:33:51Z

    is anyone working on the port of PostgreSQL for Alpha  FreeBSD ?? I have
    been waiting for over a year very very patiently !!!
    
    I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
    but postgresql does not build.
    
    If they need a box I am more than willing to give them complete access
    to my Alpha !
    
    please let me know
    
    thank you
    
    nathan
    
    
    
  2. Re: Alpha FreeBSD port of PostgreSQL !!!

    Alfred Perlstein <bright@wintelcom.net> — 2000-11-04T00:00:41Z

    * Nathan Boeger <nathan@khmere.com> [001103 15:43] wrote:
    > is anyone working on the port of PostgreSQL for Alpha  FreeBSD ?? I have
    > been waiting for over a year very very patiently !!!
    > 
    > I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
    > but postgresql does not build.
    > 
    > If they need a box I am more than willing to give them complete access
    > to my Alpha !
    > 
    > please let me know
    
    Part of the problem is that Postgresql assumes FreeBSD == -m486, since
    I have absolutely no 'configure/automake' clue it's where I faltered
    when initially trying to compile on FreeBSD.
    
    I have access to a FreeBSD box through the FreeBSD project and would
    like to have another shot at it, but I was hoping one of the guys
    more initmate with autoconf could lend me a hand.
    
    thanks,
    -- 
    -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
    "I have the heart of a child; I keep it in a jar on my desk."
    
    
  3. Re: Alpha FreeBSD port of PostgreSQL !!!

    Peter Eisentraut <peter_e@gmx.net> — 2000-11-04T00:06:08Z

    Nathan Boeger writes:
    
    > I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
    > but postgresql does not build.
    
    If I were to take a guess, then you need to add
    
    // snip
    #elif defined(__alpha__)
    typedef long int slock_t;
     
    #define HAS_TEST_AND_SET
    // snip
    
    into src/include/port/freebsd.h to get it to build.  Whether it runs is
    another question.  But with the amount of detail you provided, no one can
    tell.
    
    -- 
    Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/
    
    
    
  4. Re: [HACKERS] Alpha FreeBSD port of PostgreSQL !!!

    nathan@khmere.com — 2000-11-04T00:09:45Z

    Nathan Boeger wrote:
    
    > is anyone working on the port of PostgreSQL for Alpha  FreeBSD ?? I have
    > been waiting for over a year very very patiently !!!
    >
    > I really love my Alpha FreeBSD box and I want to use PostgreSQL on it...
    > but postgresql does not build.
    >
    > If they need a box I am more than willing to give them complete access
    > to my Alpha !
    >
    > please let me know
    >
    > thank you
    >
    > nathan
    
    Well I'am new to "hacking" but I did get it once to compile by removing the
    CFLAGS entirely (very weak !)
    
    so if you need a hand (you might have to hold mine just a little) then let
    me know. As I said I don't mind giving you access to my box (root) cause I
    cannot use it since I don't have a database on it....
    
    
    let me know
    
    
    nathan
    
    
    
  5. Re: Alpha FreeBSD port of PostgreSQL !!!

    Peter Eisentraut <peter_e@gmx.net> — 2000-11-04T00:21:12Z

    Alfred Perlstein writes:
    
    > Part of the problem is that Postgresql assumes FreeBSD == -m486,
    
    If that's all then go into src/template/freebsd and remove it.
    
    The interesting question is whether the spinlock code, which was written
    for Alpha/Linux, works (src/include/storage/s_lock.h).  All the rest
    should work out of the box.
    
    -- 
    Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/
    
    
    
  6. Re: Alpha FreeBSD port of PostgreSQL !!!

    Alfred Perlstein <bright@wintelcom.net> — 2000-11-04T00:51:15Z

    * Peter Eisentraut <peter_e@gmx.net> [001103 16:16] wrote:
    > Alfred Perlstein writes:
    > 
    > > Part of the problem is that Postgresql assumes FreeBSD == -m486,
    > 
    > If that's all then go into src/template/freebsd and remove it.
    
    ok, thanks for the pointer, I'll try to have some patches in the
    near future.
    
    > The interesting question is whether the spinlock code, which was written
    > for Alpha/Linux, works (src/include/storage/s_lock.h).  All the rest
    > should work out of the box.
    
    I'll see. :)
    
    -- 
    -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
    "I have the heart of a child; I keep it in a jar on my desk."
    
    
  7. Re: [HACKERS] Alpha FreeBSD port of PostgreSQL !!!

    Tom Lane <tgl@sss.pgh.pa.us> — 2000-11-04T01:26:48Z

    Nathan Boeger <nathan@khmere.com> writes:
    > is anyone working on the port of PostgreSQL for Alpha  FreeBSD ??
    
    Not that I know about.  DEC/Compaq was kind enough to lend the project
    an Alpha for testing, but it's running Linux (RedHat 6.2).
    
    > If they need a box I am more than willing to give them complete access
    > to my Alpha !
    
    Let me get back to you after we finish wringing out the known Alpha
    portability issues on the Linux box.  What with the fmgr changes,
    7.1 has at least a shot at running cleanly on Alphas ... but there's
    still mop-up work to do.
    
    			regards, tom lane
    
    
  8. Re: [HACKERS] Alpha FreeBSD port of PostgreSQL !!!

    Marc G. Fournier <scrappy@hub.org> — 2000-11-04T03:18:23Z

    On Fri, 3 Nov 2000, Tom Lane wrote:
    
    > Nathan Boeger <nathan@khmere.com> writes:
    > > is anyone working on the port of PostgreSQL for Alpha  FreeBSD ??
    > 
    > Not that I know about.  DEC/Compaq was kind enough to lend the project
    > an Alpha for testing, but it's running Linux (RedHat 6.2).
    
    We've also got a copy of True64 to throw onto the machine, and I *have* to
    work on getting FreeBSD running on it too ... never enough hours in the
    day :(
    
    Jeff, feel like trying out the True64 install and seeing how it
    goes?  Worst case, we have to install Redhat from scratch *shrug*
    
    Tom, anything on that machine that you wanna backup?  Or its all safe? 
    
    
    
    
  9. Re: [HACKERS] Alpha FreeBSD port of PostgreSQL !!!

    Tom Lane <tgl@sss.pgh.pa.us> — 2000-11-04T03:25:18Z

    The Hermit Hacker <scrappy@hub.org> writes:
    > Jeff, feel like trying out the True64 install and seeing how it
    > goes?  Worst case, we have to install Redhat from scratch *shrug*
    
    > Tom, anything on that machine that you wanna backup?  Or its all safe? 
    
    No problem for me.  Just keep us posted on which OS it's running today
    ;-)
    
    			regards, tom lane
    
    
  10. Re: [HACKERS] Alpha FreeBSD port of PostgreSQL !!!

    Marc G. Fournier <scrappy@hub.org> — 2000-11-04T03:37:23Z

    On Fri, 3 Nov 2000, Tom Lane wrote:
    
    > The Hermit Hacker <scrappy@hub.org> writes:
    > > Jeff, feel like trying out the True64 install and seeing how it
    > > goes?  Worst case, we have to install Redhat from scratch *shrug*
    > 
    > > Tom, anything on that machine that you wanna backup?  Or its all safe? 
    > 
    > No problem for me.  Just keep us posted on which OS it's running today
    > ;-)
    
    Will do, I know that Jeff has been antsy since True64 got in the other
    day, so I don't imagine its gonna take him long to get that installed :)
    
    
    
    
    
  11. How do you call one pltcl procedure from another?

    Jonathan Ellis <jellis@advocast.com> — 2000-11-04T18:31:25Z

    I defined a procedure
    
    CREATE FUNCTION meta_class (varchar) RETURNS varchar AS '
    ...
    ' LANGUAGE 'pltcl';
    
    This works fine.  But when I want to call it from another tcl procedure I
    get errors:
    bf2=# CREATE FUNCTION foo (varchar) RETURNS varchar AS '
        return [meta_class $1]
    ' LANGUAGE 'pltcl';
    
    bf2'# bf2'# CREATE
    
    bf2=# bf2=# select foo(class) from weapon_Types;
    ERROR:  pltcl: invalid command name "meta_class"
    
    This IS possible -- isn't it?
    
    -Jonathan