libgcc_s.so.1 missing from filesystem
I built several utilities including python using buildroot. A commom problem seems to be that they depend on a library libgcc.so.1 which appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, but does not get transferred to the target filesystem. Manually moving it to the target appears to be a workaround. Is there a more elegant solution? What is this library?
Regards,
Dave.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dave.vcf
Type: text/x-vcard
Size: 288 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061011/9a160e44/attachment.vcf
Quoted 3 lines · David Lambert
A commom problem seems to be that they depend on a library libgcc.so.1 which appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, [...] Is there a more elegant solution?
One possible solution is to unset BR2_GCC_SHARED_LIBGCC in the buildroot configuration, to get rid of the shared libgcc alltogether.
Information on libgcc can be found here:
http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html
Cheers // Fredrik Roubert
Signature · 9 lines
Visserij 192 | +32 473 344527 / +46 708 776974 BE-9000 Gent | http://www.df.lth.se/~roubert/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 303 bytes Desc: not available Url : http://busybox.net/lists/buildroot/attachments/20061011/8648f995/attachment.pgp
Quoted 7 lines · Fredrik Roubert
Quoted 3 lines · David Lambert
A commom problem seems to be that they depend on a library libgcc.so.1 which appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, [...] Is there a more elegant solution?
Quoted 10 lines
One possible solution is to unset
BR2_GCC_SHARED_LIBGCCin the buildroot configuration, to get rid of the shared libgcc alltogether.Information on libgcc can be found here:
http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html
Cheers // Fredrik Roubert
I haven't narrowed it down to exactly which version of Buildroot stopped deploying the libgcc_so.1, but I've found that an older cataloged version in our source control was deploying that library properly. The newer version of buildroot tends to skip over a few other libraries as well.
Regards
Signature · 4 lines
~ Ashwin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20061011/f685ef7c/attachment.htm
Quoted 4 lines · Ashwin Bihari
I haven't narrowed it down to exactly which version of Buildroot stopped deploying the libgcc_so.1, but I've found that an older cataloged version in our source control was deploying that library properly. The newer version of buildroot tends to skip over a few other libraries as well.
details?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
Quoted 6 lines · Erik Andersen
Quoted 2 lines · Ashwin Bihari
I haven't narrowed it down to exactly which version of Buildroot stopped deploying the libgcc_so.1, but I've found that an older cataloged
version in
Quoted 1 line
our source control was deploying that library properly. The newer
Quoted 8 lines
version of
Quoted 1 line
buildroot tends to skip over a few other libraries as well.
details?
-Erik
Erik,
My .config is attached and I'm using the snapshot of Buildroot from Oct 9th.
Thanks
Signature · 11 lines
~ Ashwin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20061017/718e20fe/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: buildroot.config Type: application/octet-stream Size: 9938 bytes Desc: not available Url : http://busybox.net/lists/buildroot/attachments/20061017/718e20fe/attachment.obj
Quoted 6 lines · David Lambert
I built several utilities including python using buildroot. A commom problem seems to be that they depend on a library libgcc.so.1 which appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, but does not get transferred to the target filesystem. Manually moving it to the target appears to be a workaround. Is there a more elegant solution? What is this library?
Could I have a copy of your buildroot .config file? I've tested both with and without BR2_GCC_SHARED_LIBGCC set and both settings produced working root filesystems for me....
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
Quoted 4 lines · Erik Andersen
Could I have a copy of your buildroot .config file? I've tested both with and without
BR2_GCC_SHARED_LIBGCCset and both settings produced working root filesystems for me....
Erik,
I removed my manual copy and it now works! The only change is that I
have since run svn update (to revision 16401). Unfortunately I do not remember the revision where the problem occurred. In any case I am including my .config file as you requested.
Best regards,
Dave.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
Url: http://busybox.net/lists/buildroot/attachments/20061018/01912809/attachment.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dave.vcf
Type: text/x-vcard
Size: 288 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061018/01912809/attachment-0001.vcf