Date: Tue, 25 Oct 2005 00:04:23 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 639 ************************************************** Monday 24 October 2005 Number 639 ************************************************** Subjects for today 1 help linking please : dave bamford 2 Re: help linking please : Franz Bakan" 3 Re: help linking please : dave bamford 4 Re: gdb for gcc 3.3.2 and 3.3.5? : Jon Saxton **= Email 1 ==========================** Date: Sun, 23 Oct 2005 17:21:53 +0100 From: dave bamford Subject: help linking please Hi I am making good progress with porting BoxBackup from a port that was done for win32, but I am stuck and hope someone on this list can help me out please. All the modules compile with the makefiles and I get an executable here are the last few lines of the make phase make[1]: `../../release/lib/backupclient/backupclient.a' is up to date. make[1]: Leaving directory `/ports/box0.09h/box/lib/backupclient' g++ -o ../../release/bin/bbackupd/bbackupd .../../release/bin/bbackupd/BackupClientContext.o .../../release/bin/bbackupd/BackupClientDeleteList.o .../../release/bin/bbackupd/BackupClientDirectoryRecord.o .../../release/bin/bbackupd/BackupClientInodeToIDMap.o .../../release/bin/bbackupd/BackupDaemon.o .../../release/bin/bbackupd/bbackupd.o .../../release/lib/backupclient/backupclient.a .../../release/lib/server/server.a ../../release/lib/crypto/crypto.a .../../release/lib/compress/compress.a ../../release/lib/common/common.a -lssl -lcrypto -lz -lpoll epm: D:\ports\box0.09h\box\bin\bbackupd > I had to edit the makefiles as there was no autoconfigure and configure was a perl program. I now get this if I try to run the output [D:\ports\box0.09h\box\release\bin\bbackupd]bbackupd SYS0191: D:\ports\box0.09h\box\release\bin\bbackupd\bbackupd.exe cannot be run in an OS/2 session. BTW I renamed bbackupd to bbackupd.exe I used gcc 3.3.5. I suspect I am not using the correct switches for linking or should be using another linker? Thanks Dave Bamford. **= Email 2 ==========================** Date: Sun, 23 Oct 2005 20:21:21 +0200 (CEST) From: "Franz Bakan" Subject: Re: help linking please On Sun, 23 Oct 2005 17:21:53 +0100, dave bamford wrote: >I now get this if I try to run the output >[D:\ports\box0.09h\box\release\bin\bbackupd]bbackupd >SYS0191: D:\ports\box0.09h\box\release\bin\bbackupd\bbackupd.exe cannot >be run in an OS/2 session. > >BTW I renamed bbackupd to bbackupd.exe instead of renaming try emxbind bbackupd instead Franz **= Email 3 ==========================** Date: Sun, 23 Oct 2005 21:38:38 +0100 From: dave bamford Subject: Re: help linking please Franz Bakan wrote: >On Sun, 23 Oct 2005 17:21:53 +0100, dave bamford wrote: > > > >>I now get this if I try to run the output >>[D:\ports\box0.09h\box\release\bin\bbackupd]bbackupd >>SYS0191: D:\ports\box0.09h\box\release\bin\bbackupd\bbackupd.exe cannot >>be run in an OS/2 session. >> >>BTW I renamed bbackupd to bbackupd.exe >> >> > >instead of renaming try > emxbind bbackupd >instead > >Franz > > > Thanks I solved the problem by editing the make file to -o bbackupd.exe the .exe makes an os2 exe. Got the app built and running see www.fluffy.co.uk/boxbackup for details Dave. **= Email 4 ==========================** Date: Sun, 23 Oct 2005 22:27:14 -0400 From: Jon Saxton Subject: Re: gdb for gcc 3.3.2 and 3.3.5? Worked like a charm - until I tried to run the executable. It was mostly full of zeros. Oddly enough, other methods of creating files work fine - for example, using a text editor, or copying from another location. I suspect that the driver doesn't support the full range of APIs. I had a look at TVFS because that also seems to have a way of limiting the free space report and I even thought about writing a system hook to do it but ultimately I solved the problem by doing something I had been intending to do anyway, and that was to dispense with shared folders on Virtual PC in favour of using network sharing. In other words, instead of having an OS2 directory on my Windows XP machine made visible directly to the virtual machine as an O: drive, I set up a NetBIOS share instead and did a "net use" from the OS/2 virtual machine. The problem with ILink went away. That was a good start but there are significant advantages to using network sharing rather than shared folders with Virtual PC. OS/2 works a lot better when it can write extended attributes. Shared folders don't permit that whereas NetBIOS sharing does. It appears to me that NTFS has full support for extended attributes but it is only accessible via NetBIOS calls. NetBIOS I/O seems to be a lot faster than shared folder I/O as well. Everything is working nicely now. Thans to everyone for all the advice. Sebastian Wittmeier wrote: > Hi Jon, > you could use Netdrive. It has an option to mount local file systems > and set the free space to an arbitrary value. > I don't know how much the performance suffers when compiling. > > Sebastian > > > Jon Saxton wrote: > >> Most of the problems went away with the new VAC++ install and, in >> particular, with the updated ILink. The LNK1081 error "No space for >> NB04" persists. The problem seems to be that I am building on a drive >> with almost 70 Gb of free space. When I ran on a drive with a few >> hundred Mb free then everything worked. >> >> Switching to a new drive isn't really an option since my sources have to >> be visible on OS/2 and Windows (and soon on Linux). They reside on a >> Windows directory which is seen as a shared directory on OS/2 under >> Virtual PC. >> >> I thought there was a gizmo which intercepted the call to get the free >> space on a drive and reported a fake number but I couldn't find it on a >> quick search of Hobbes. There is spacehog but that seems to fill the >> drive with temporary files - something which is not an option on a >> shared disk. >> >> I wish life would be simple, sometimes. > > > > > > -- Jon Saxton Shopkeeper, Numismatist-in-training Developer of cross-platform software for UNIX, OS/2 and Windows U.S. Agent for Triton Technologies International Ltd http://www.triton.vg/