From: | Jonathan Stone <jonathan(at)DSG(dot)Stanford(dot)EDU> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane), current-users(at)netbsd(dot)org, jonathan(at)DSG(dot)Stanford(dot)EDU |
Subject: | Re: [HACKERS] More on shared objects problem |
Date: | 1999-07-27 17:49:49 |
Message-ID: | 199907271749.KAA27060@Cup.DSG.Stanford.EDU |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>If it helps, here is the output of "file /netbsd" which tells you for
>sure it is an ELF system.
>
>/netbsd: ELF 32-bit LSB executable, Intel 80386, version 1, statically linke
>d, not stripped
>
>so;
>
>if [ "`file /netbsd | cut -d' ' -f2`" = "ELF" ]
>then elf=yes
>fi
>
>Under the netbsd secion of configure_in should do it.
It's worth getting this really right during the migration to ELF...
That test doesn't work on pmax systems which have ECOFF-format kernels
(for netbooting) and ELF userland. A `clean' test that asks the kernel
what format(s) it supports would be nice; absent that, testing on
userland binaries as well --say /usr/libexec/ld.elf_so (or maybe
instead?) is safer than relying on the format of the kernel itself.
From | Date | Subject | |
---|---|---|---|
Next Message | Todd Vierling | 1999-07-27 18:00:28 | Re: More on shared objects problem |
Previous Message | David Brownlee | 1999-07-27 17:45:55 | Re: [HACKERS] More on shared objects problem |