OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: ccrandal on June 13, 2004, 11:14:13 pm

Title: Problem with ar on Cacko 1.21b ROM
Post by: ccrandal on June 13, 2004, 11:14:13 pm

I\'m receiving the following error when using ar to extract a Debian binary package format version 2:

ar: error while loading shared libraries: libbfd-2.9.5.0.14.so: cannot load shared object file: No such file or directory

Is anyone else getting this error?

Thanks
Curt

Title: Problem with ar on Cacko 1.21b ROM
Post by: datajerk on June 13, 2004, 11:28:15 pm

Not here, also using 1.21b.

\'which ar\' should return /usr/bin/ar and md5sum return: 1554bab25f6c3251ebfac119aca020a8  /usr/bin/ar

You should also have this link:

/usr/lib/libbfd-2.9.5.0.14.so -] /usr/lib.rom/libbfd-2.9.5.0.14.so

Title: Problem with ar on Cacko 1.21b ROM
Post by: BalroG on June 14, 2004, 09:02:15 am

Where can one get \"ar\" for the Z?

On the default Sharp ROM it is not on the system(I will hopefully get around to flashing to Cacko in the next week.)

Thanks!!

Title: Problem with ar on Cacko 1.21b ROM
Post by: datajerk on June 14, 2004, 09:59:19 am

binutils ipk I believe.

Title: Problem with ar on Cacko 1.21b ROM
Post by: ccrandal on June 14, 2004, 05:31:50 pm

I see the problem now.  On my CF card, I have dev_img-1.5 installed and mounted.  Somehow, the link:

/home/root/usr/lib/libbfd-2.9.5.0.14.so -]
/home/zaurus/develop/lib/libbfd-2.9.5.0.14.so

was established.  Well, not only does libbfd-2.9.5.0.14.so not exist in the dev_img-1.5 image, but even if it were that would usually be a dead link as I don\'t use that CF card often.

I just repointed that link to the lib in the ROM and it all works fine now.

Title: Problem with ar on Cacko 1.21b ROM
Post by: ccrandal on June 14, 2004, 05:32:47 pm

BTW, thanks datajerk!

Title: Problem with ar on Cacko 1.21b ROM
Post by: maslovsky on June 15, 2004, 11:45:35 am

Quote

I see the problem now.  On my CF card, I have dev_img-1.5 installed and mounted.  Somehow, the link:

/home/root/usr/lib/libbfd-2.9.5.0.14.so -]
/home/zaurus/develop/lib/libbfd-2.9.5.0.14.so

was established.  Well, not only does libbfd-2.9.5.0.14.so not exist in the dev_img-1.5 image, but even if it were that would usually be a dead link as I don\'t use that CF card often.

I just repointed that link to the lib in the ROM and it all works fine now.

Thanks for the finding! Ar in dev-img is supposed to work, but I may have broken it somehow...  The one in ROM should be good enough theough.

Title: Problem with ar on Cacko 1.21b ROM
Post by: ccrandal on June 15, 2004, 06:50:21 pm

Yep, the one in the ROM works great.  Is there a reason you also bundled that lib in the dev-img too?

Well, I\'ve got ar working and can get at my ipk\'s contents.  Now I want to zip it back up into something ipkg can read.  I noticed that tar doesn\'t support compression on the Z.  So, I went on my Mac and used Darwin\'s tar.  While `file` says it\'s exactly the same file type as all my other ipks, it would not install.

So, I popped the file back on my Z, extracted the contents, and then separately tar\'d and gzip\'d the archive.  Now I get:

zcat: stdin: unexpected end of file
ipkg_install_file: ERROR unpacking control.tar.gz from libpcap0_0.7.2-1_arm.ipk

I don\'t have my Mac on me, but I could try `gtar cvzf`and if that works.  But I think it\'d be easier to just create a bash script on the Z to convert the files.  Using the tools on the Z, what command would I need to execute to build a proper ipk?

Thanks
Curt

Title: Problem with ar on Cacko 1.21b ROM
Post by: maslovsky on June 16, 2004, 05:51:09 am

Quote

Yep, the one in the ROM works great.  Is there a reason you also bundled that lib in the dev-img too?

Just a leftover I guess...

Quote

Well, I\'ve got ar working and can get at my ipk\'s contents.  Now I want to zip it back up into something ipkg can read.  I noticed that tar doesn\'t support compression on the Z.  

No it does not. You\'ll need to compress tar file separately using gzip.