[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-02-22 Thread Christopher Bergström
apologies for the noise.. preg_list.* wasn't being generated correctly because of ksh93.. Using bash as the shell and I get progress.. Next issue I hit... BUILD_OS seems like it's still defined as LINUX.. changing that to SUNOS == unhappy.. (What's the cleanest way to add this?) looking at elf_

[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-02-22 Thread Christopher Bergström
On Thu, Jan 29, 2009 at 3:04 PM, John Martin wrote: > C. Bergstr?m wrote: >> >> >> I just glanced at it, but looks like Elf32_Word and friends is undefined.. >> >> ../include/elf_stuff.h:57:23: warning: sys/cdefs.h: No such file or >> directory >> >> pm me if you'd like access to the env to help o

[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-01-29 Thread John Martin
C. Bergstr?m wrote: > > > I just glanced at it, but looks like Elf32_Word and friends is > undefined.. > > ../include/elf_stuff.h:57:23: warning: sys/cdefs.h: No such file or > directory > > pm me if you'd like access to the env to help or look around. > > This is in the linux include directory.

[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-01-29 Thread "C. Bergström"
Joerg Schilling wrote: > "C. Bergstr?m" wrote: > > >> Thanks a lot for letting me know this.. I'm not sure it's something we >> can send upstream, but maybe the open64 guys can make a suggestion? I'd >> much rather link/use maintained code instead of the roll-your-own >> approach for every

[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-01-28 Thread "C. Bergström"
John Martin wrote: > Joerg Schilling wrote: >> John Martin wrote: >> >> >>> This biggest headache I had doing the port was asprintf()/vasprintf(). >>> There was a lot of code that used these functions. Once we have >>> this with b107, >>> it will make things a lot easier. >>> >> >> With t

[hpcdev-discuss] [OSUNIX-dev] Re: Porting open64 to solaris

2009-01-27 Thread John Martin
Joerg Schilling wrote: > John Martin wrote: > > >> This biggest headache I had doing the port was asprintf()/vasprintf(). >> There was a lot of code that used these functions. Once we have this >> with b107, >> it will make things a lot easier. >> > > With the private format() based prin