Building 64 bit Python against 32 bit ASE on 64-bit Linux

I've been using various version of
SYBASE=/usr/local/packages/sybase* to no avail. They all are
giving me errors lated to "libblk". any ideas?

/usr/bin/ld: skipping incompatible
/usr/local/packages/sybase_OLD/lib/libblk.a when searching
for -lblk

If possible could you CC mrogish at tigr dot org since I am
using the Sybase.com forums reader and it is difficult to
bookmark this thread.

Thanks!!!

--
Matt Rogish

cronus:/local/src/Linux64/python/modules/sybase-0.37 #
/usr/local/packages/python64-2.4.2/bin/python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.4
copying Sybase.py -> build/lib.linux-x86_64-2.4
running build_ext
building 'sybasect' extension
creating build/temp.linux-x86_64-2.4
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
blk.c -o build/temp.linux-x86_64-2.4/blk.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
databuf.c -o build/temp.linux-x86_64-2.4/databuf.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
cmd.c -o build/temp.linux-x86_64-2.4/cmd.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
conn.c -o build/temp.linux-x86_64-2.4/conn.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
ctx.c -o build/temp.linux-x86_64-2.4/ctx.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
datafmt.c -o build/temp.linux-x86_64-2.4/datafmt.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
iodesc.c -o build/temp.linux-x86_64-2.4/iodesc.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
locale.c -o build/temp.linux-x86_64-2.4/locale.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
msgs.c -o build/temp.linux-x86_64-2.4/msgs.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
numeric.c -o build/temp.linux-x86_64-2.4/numeric.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
money.c -o build/temp.linux-x86_64-2.4/money.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
datetime.c -o build/temp.linux-x86_64-2.4/datetime.o
/usr/local/packages/gcc-3.4.4/bin/gcc -fno-strict-aliasing
-DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE
-DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER
-DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC
-DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC
-DHAVE_CS_CMP -I/usr/local/packages/sybase_OLD/include
-I/usr/local/packages/python64-2.4.2/include/python2.4 -c
sybasect.c -o build/temp.linux-x86_64-2.4/sybasect.o
/usr/local/packages/gcc-3.4.4/bin/gcc -pthread -shared
-L/usr/local/packages/gcc-3.4.4/lib64
-Wl,-R,/usr/local/packages/gcc-3.4.4/lib64
-I/usr/local/packages/gcc-3.4.4/include
-I/usr/local/packages/gcc-3.4.4/include
build/temp.linux-x86_64-2.4/blk.o
build/temp.linux-x86_64-2.4/databuf.o
build/temp.linux-x86_64-2.4/cmd.o
build/temp.linux-x86_64-2.4/conn.o
build/temp.linux-x86_64-2.4/ctx.o
build/temp.linux-x86_64-2.4/datafmt.o
build/temp.linux-x86_64-2.4/iodesc.o
build/temp.linux-x86_64-2.4/locale.o
build/temp.linux-x86_64-2.4/msgs.o
build/temp.linux-x86_64-2.4/numeric.o
build/temp.linux-x86_64-2.4/money.o
build/temp.linux-x86_64-2.4/datetime.o
build/temp.linux-x86_64-2.4/sybasect.o
-L/usr/local/packages/sybase_OLD/lib -lblk -lct -lcs
-lsybtcl -lcomn -lintl -o
build/lib.linux-x86_64-2.4/sybasect.so
/usr/bin/ld: skipping incompatible
/usr/local/packages/sybase_OLD/lib/libblk.a when searching
for -lblk
/usr/bin/ld: cannot find -lblk
collect2: ld returned 1 exit status
error: command '/usr/local/packages/gcc-3.4.4/bin/gcc'
failed with exit status 1
cronus:/local/src/Linux64/python/modules/sybase-0.37 #
0
Matt
11/7/2005 7:13:37 PM
sybase.ase.linux 1395 articles. 0 followers. Follow

3 Replies
1922 Views

Similar Articles

[PageSpeed] 20

> I've been using various version of
> SYBASE=/usr/local/packages/sybase* to no avail. They all
> are giving me errors lated to "libblk". any ideas?
>
> /usr/bin/ld: skipping incompatible
> /usr/local/packages/sybase_OLD/lib/libblk.a when searching
> for -lblk

You can't mix 32bit and 64bit code in the same binary.

You either need to rebuild python in 32bit mode, or somehow
get the 64bit libraries from Sybase...

Michael
0
mpeppler
11/8/2005 7:53:28 AM
Thanks to Dan Gomez here at TIGR, we have a working patch!
---
Here's a working dynamic patch for both x86 archs  :-) .
But I rely on 'uname' command (not ideal but then again, if
they are
missing that they probably have bigger issues)

# diff -Naur sybase-0.37/setup.py sybase-0.37.patch/setup.py
--- sybase-0.37/setup.py        2005-04-06
18:46:43.000000000 -0400
+++ sybase-0.37.patch/setup.py  2005-11-08
10:44:26.840499000 -0500
@@ -45,7 +45,12 @@
     # On Linux the Sybase tcl library is distributed as
sybtcl
     syb_libs = []
     if os.uname()[0] == 'Linux':
-        lib_names = ['blk', 'ct', 'cs', 'sybtcl', 'insck',
'comn',
'intl']
+        # accomodate 64-bit sybase libraries
+        arch = os.popen("uname -m").read().splitlines()[0]
+       if "x86_64" == arch:
+          lib_names = ['blk64', 'ct64', 'cs64', 'sybtcl64',
'insck64',
'comn64', 'intl64']
+       else:
+           lib_names = ['blk', 'ct', 'cs', 'sybtcl',
'insck', 'comn',
'intl']
     elif os.uname()[0] == 'AIX':
         lib_names = ['blk', 'ct', 'cs', 'comn', 'tcl',
'intl', 'insck']
     else:

Now tuck the above patch (not including the diff command
line) into a
file called 'patch1' and call the 'patch' command

# ls -ld sybase-0.37*
drwxr-xr-x  4  500 staff  4096 Nov  8 10:50 sybase-0.37
drwxr-xr-x  5  500 staff  4096 Nov  8 10:47
sybase-0.37.patch
-rw-r--r--  1 root root  95081 Apr  6  2005
sybase-0.37.tar.gz

# patch -p0 <patch1
patching file sybase-0.37/setup.py

Done.

--
Matt

> You can't mix 32bit and 64bit code in the same binary.
>
> You either need to rebuild python in 32bit mode, or
> somehow get the 64bit libraries from Sybase...
>
> Michael
0
Matt
11/8/2005 3:13:07 PM
While you are at it - remember that with ASE 15 all the libraries are
called syb... (libsybct.so, etc).

Michael

On Tue, 08 Nov 2005 08:13:07 -0700,  wrote:

> Thanks to Dan Gomez here at TIGR, we have a working patch! ---
> Here's a working dynamic patch for both x86 archs  :-) . But I rely on
> 'uname' command (not ideal but then again, if they are
> missing that they probably have bigger issues)
> 
> # diff -Naur sybase-0.37/setup.py sybase-0.37.patch/setup.py ---
> sybase-0.37/setup.py        2005-04-06 18:46:43.000000000 -0400
> +++ sybase-0.37.patch/setup.py  2005-11-08 10:44:26.840499000 -0500
> @@ -45,7 +45,12 @@
>      # On Linux the Sybase tcl library is distributed as
> sybtcl
>      syb_libs = []
>      if os.uname()[0] == 'Linux':
> -        lib_names = ['blk', 'ct', 'cs', 'sybtcl', 'insck', 'comn',
> 'intl']
> +        # accomodate 64-bit sybase libraries +        arch =
> os.popen("uname -m").read().splitlines()[0] +       if "x86_64" == arch:
> +          lib_names = ['blk64', 'ct64', 'cs64', 'sybtcl64', 'insck64',
> 'comn64', 'intl64']
> +       else:
> +           lib_names = ['blk', 'ct', 'cs', 'sybtcl', 'insck', 'comn',
> 'intl']
>      elif os.uname()[0] == 'AIX':
>          lib_names = ['blk', 'ct', 'cs', 'comn', 'tcl',
> 'intl', 'insck']
>      else:
> 
> Now tuck the above patch (not including the diff command line) into a
> file called 'patch1' and call the 'patch' command
> 
> # ls -ld sybase-0.37*
> drwxr-xr-x  4  500 staff  4096 Nov  8 10:50 sybase-0.37 drwxr-xr-x  5  500
> staff  4096 Nov  8 10:47 sybase-0.37.patch
> -rw-r--r--  1 root root  95081 Apr  6  2005 sybase-0.37.tar.gz
> 
> # patch -p0 <patch1
> patching file sybase-0.37/setup.py
> 
> Done.
> 
> --
> Matt
> 
>> You can't mix 32bit and 64bit code in the same binary.
>>
>> You either need to rebuild python in 32bit mode, or somehow get the
>> 64bit libraries from Sybase...
>>
>> Michael

-- 
Michael Peppler [TeamSybase] mpeppler@peppler.org - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html


0
Michael
11/8/2005 4:15:25 PM
Reply:

Similar Artilces:

Upgrading from ASE (32-bit) 12.0.0.7 on Solaris 2.8 64-bit to ASE(64-bit) 12.5.1 on Solaris 64-bit
Hello all, We are planning to upgrade our ASE servers from a 32-bit ASE 12.0.0.7 to 64-bit ASE 12.5.1 on Solaris 8. Could you please give what are the steps to be taken care and how do I start with ( Do I have to first upgrade to 32-bit12.5.1 and then upgrade to 64-bit ASE 12.5.1, or directly upgrade from 32-bit 12.0.0.7 to 64-bit 12.5.1 ?). Could you also please point to some documentation (about upgrading 32-bit 12.0.0.7 to 64-bit 12.5.1). Thanks RK ...

dump and load from 64-bit Solaris/32-bit ASE .. to .. AMD64/32-bit ASE
Will a cross-platform load be done by Sybase ASE if the dump was made from 64-bit Solaris9 / 32-bit ASE and the load database is to be done on AMD64 / 32-bit ASE ?? What about from 64-bit Solaris9 / 32-bit ASE .. to AMD64 / 64-bit ASE ?? On Sun, 18 Sep 2005 17:27:19 -0700, Jesus M. Salvo Jr. wrote: > > Will a cross-platform load be done by Sybase ASE if the dump was made from > 64-bit Solaris9 / 32-bit ASE and the load database is to be done on AMD64 > / 32-bit ASE ?? > > What about from 64-bit Solaris9 / 32-bit ASE .. to AMD64 / 64-bit ASE ?? Yes, tha...

32-bit ASE 12.5.x on 64-bit Solaris9 or 64-bit Solaris10
manuals.sybase.com does not mention anything about Solaris9/10. It only mentions about required patches for Solaris8. Does Sybase support 32-bit ASE 12.5.x on 64-bit Solaris9 or 64-bit Solaris10 ( SPARCs of course )? Any specific OS patches required for Sol9/10 ? ...

ASE 64 bit for Linux AMD64 bit
Any knows if ASE 12.xx.xx 64 bit for Linux (Fedora Core2 64bit) AMD 64 bit CPU is avaialable now? Last time I called Sybase Customer Service they said it should be available by Fall 2004. Thanks On Thu, 02 Dec 2004 10:33:30 -0800, dono wrote: > Any knows if ASE 12.xx.xx 64 bit for Linux (Fedora Core2 > 64bit) AMD 64 bit CPU is avaialable now? I haven't seen any announcement. Sybase just released 12.5.3 - my guess (but it's only a guess!) is that this will be forthcoming in the next few weeks. Michael -- Michael Peppler [TeamSybase] mpeppler@peppler.org - ht...

32-bit build of TraceMonkey on 64-bit Linux
Hi, Andreas told me that TraceMonkey doesn't work on 64-bit Linux; 'js -j' just runs SpiderMonkey. So I'm trying to do a 32-bit build of 'js' on my 64-bit Ubuntu Linux box. I tried: ./configure --disable-optimize --enable-debug --target=3Di386- unknown-linux-gnu make (my default target is "x86_64-unknown-linux-gnu") but I get lots of compile errors: jscpucfg.cpp:48:21: error: prtypes.h: No such file or directory jscpucfg.cpp:206:2: error: #error "Endianess not defined." jscpucfg.cpp:103: error: =91PRInt64...

Performance advantage of ASE 64 Bit over ASE 32 Bit version
Hi Folks, Is any there any performance gains when using ASE 64 bit versus ASE 32 bit version like larger memory gains hence good performance? Thanks Jayesh The more memory , the more data you can cache, the better performance. <Jayesh> wrote in message news:4460bb13.194c.1681692777@sybase.com... > Hi Folks, > > Is any there any performance gains when using ASE 64 bit > versus ASE 32 bit version like larger memory gains hence > good performance? > > > Thanks > Jayesh > The more memory , the more data you can cache, the better...

ASE 64 bit AMD 64 Xeon 32 bit and Support
Got a question for the experts. We are looking at moving to Linux RH ES 3 or 4 for our production and backup databases. We have been running ASE on Linux as our development database for a couple of years with out any troubles. Currently ASE SBE on RHES 3. Question #1: I noticed ASE has a "released" status for AMD 64. What type of support does Sybase provide for released vs certified. I would not want our support contract to be useless if we run the 64 bit version. Question #2: Our backup server would be a 32 bit Xeon based machine. Any troubles/pitfalls doing ...

instructions for building 32-bit Linux Firefox on 64-bit system
Building 32-bit Linux Firefox on a 32-bit Linux system appears to have become challenging, so bugs like <https://bugzilla.mozilla.org/show_bug.cgi?id=857697> have switched Mozilla's Linux build systems to build it on 64-bit Linux. But instructions for doing this haven't made it to MDN's Linux Prerequisites doc <https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Linux_Prerequisites>. Is there somewhere I can find concise instructions for configuring a 64-bit system to build 32-bit Linux? Or perhaps someone in the know can update the MDN ...

Migrating from ASE 12.0 32-bit to ASE 12.0 64-bit
Has anyone run into any problems migrating from 32-bit to 64-bit? ...

Migrating from ASE 12.0 32-bit to ASE 12.0 64-bit
Has anyone run into any problems migrating from 32-bit to 64-bit? ...

Migration from ASE 12.0 32 bit to ASE 12.x 64 bit
Pundits one and all, We are looking closely at migrating from ASE 12.0.0.4 ESD#2 32 bit on a Solaris platform to 64 bit ASE. Notwithstanding improvements in ASE 12.5 that may benefit us, the main driver is to take maximum advantage of the 16G physical memory on the host. Simplistically we could either ... a) convert to 64 bit ASE 12.0 (as phase 1), then convert to ASE 12.5 64 bit (as phase 2) at a later date, or b) convert to 32 bit ASE 12.5 (as phase 1), then convert at 64 bit after gaining confidence in the version change, c) convert to 64 bit ASE 12.5 in one fell swoop to m...

Advantages of 64-bit ASE 12.5 over 32-bit ASE 12.5
What are the advantages of 64-bit Server over 32-bit server ? We are thinking of upgrading our servers from 32-bit ASE 12.0.0.7 to ASE 12.5, But we are stuck while taking a decision about 32-bit or 64-bit. Management wants to know why do we have to go 64-bit while the 32-bit works fine. Thanks RK This document is an FAQ on ASE 64-bit and may be of help: http://www/detail/1,6904,1012280,00.html The only real advantage is the ability to assign a larger amount of memory to ASE, thereby allowing for larger data caches and reduced physical io. HTH, Dave <rk> wrote ...

Difference on ASE-12 32-bit & 64-bit on IBM AIX SP-64 machine
Hello, I would like to get more information for ASE-12 upgrade on IBM AIX SP-64 machine. What is the different between ebf9311 (32-bit) and ebf9312 (64-bit) on ASE-12? Are they compatible for IBM SP-64 machine. If just install 32-bit version, what will be suffered than install 64-bit version? Elsa Elsa wrote: > I would like to get more information for ASE-12 upgrade on IBM AIX SP-64 > machine. What is the different between ebf9311 (32-bit) and ebf9312 (64-bit) > on ASE-12? The EBFs are related to the version. If you have ASE 12 (32 bit version), you n...

solaris 32 bit
i have solaris version - "SunOS soln1 5.10 Generic_118855-33 i86pc i386 i86pc" 1. can i install "ASE 15.0 Solaris 64-bit Server" for testing? 2. does anyone have links to download ASE Solaris 32-bit 12.5+ / 15 version? Raju wrote: > > i have solaris version - > "SunOS soln1 5.10 Generic_118855-33 i86pc i386 i86pc" > > 1. can i install "ASE 15.0 Solaris 64-bit Server" for > testing? If its the Solaris x64 version. > 2. does anyone have links to download ASE Solaris 32-bit > 12.5+ / 15 version? Have you ...

Web resources about - Building 64 bit Python against 32 bit ASE on 64-bit Linux - sybase.ase.linux

Auditorium Building - Wikipedia, the free encyclopedia
... -87.6251722 Coordinates : 41°52′33.95″N 87°37′30.62″W  /  41.8760972°N 87.6251722°W  / 41.8760972; -87.6251722 The Auditorium Building in ...

Facebook is giving away a powerful new technology for building smart computers
... us to improve it. We believe that this open collaboration helps foster innovation for future designs, putting us all one step closer to building ...

Kohl's is building legion of loyalists
Kohl's, which outperformed Macy's in the third quarter, is hoping to ride its momentum into the critical holiday shopping period.

Walmart Pay gives retailer strategic advantage, building off existing app
Walmart jumped out Thursday with a natively built in-store mobile payment technology that works with any iOS or Android phone and any major credit ...

Pro-Coal Democrat Pays EPA $220K For Building Ponds On His Property
Pro-Coal Democrat Pays EPA $220K For Building Ponds On His Property

Why Is Baidu Building Driverless Cars?
The company claims that its autonomous car is the first in China to have demonstrated full autonomy under mixed road conditions. The car is built ...

Stanford University Building Drone Collision Prevention Software - Fortune
Stanford University researchers are building software that can alert and prevent drones from smashing into each other.

VICIS wins $250K grant to continue building high-tech football helmet that reduces brain trauma
Vicis has more cash to help the company finish developing its high-tech football helmet. The company, which spun out of the University of Washington ...

Why Is NASA Building This Giant Soccer Ball?
Because it has a goal! But a different kind of goal to the ones found in soccer: instead, it’s one to put American astronauts on Mars. Read ...

PA student protesters want building renamed because it honors someone named “Lynch”
... were on display, but the students had one additional demand which essentially broke the irony meter. They want a long standing college building ...

Resources last updated: 12/14/2015 11:15:44 AM