archive-org.com » ORG » U » UCLIBC.ORG

Total: 63

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • uClibc
    epoll h updates ldd host misc corrections Enjoy Iff you experience problems with this release then please file a bug 11 April 2012 uClibc 0 9 33 1 Released uClibc 0 9 33 1 was released today Grab the current 0 9 33 1 release tarball Refer to the ChangeLog 0 9 33 0 9 33 1 for the gory details or find and use other interresting stuff in the download area Changes include NPTL Fix static linking with signal related functions Add a microblaze specific sys user h stdio prevent retries on fclose fflush after write errors stdio Fix char signedness in load inttype fchmodat fix handling of flags libdl fix memleak for local scope of dlopened s needed libraries ldso fix fdpic support broken from prelink patch inotify rm watch Change second argument to int alpha trim crt code to fix build errors mmap64 always use unsigned 64bit offsets Enjoy 1 Feb 2012 uClibc 0 9 33 Released uClibc 0 9 33 was released today Grab the current 0 9 33 release tarball Refer to the ChangeLog 0 9 32 1 0 9 33 for an in depth description of changes Enjoy 30 Dec 2011 uClibc 0 9 33 rc1 Released Release candidate 1 for the upcoming 0 9 33 was released today Go to the downloads page and grab 0 9 33 rc1 release candidate See ChangeLog 0 9 32 1 0 9 33 rc1 for details Please test and report back to the mailing list 30 Dec 2011 uClibc 0 9 32 1 Released 0 9 32 1 is a bug fix release and a recommended update Head to the downloads page to pick up the 0 9 32 1 release The ChangeLog 0 9 32 0 9 32 1 has all the details Enjoy 08

    Original URL path: http://www.uclibc.org/ (2015-03-26)
    Open archived version from archive


  • uClibc
    i386 i960 ia64 m68k mips mipsel PowerPC SH SPARC and v850 processors If you are building an embedded Linux system and you find that glibc is eating up too much space you may want to consider using uClibc If you are building a huge fileserver with 12 Terabytes of storage then using glibc may make more sense Unless for example that 12 Terabytes will be Network Attached Storage and you plan to burn Linux into the system s firmware uClibc is maintained by Erik Andersen and is licensed under the GNU LESSER GENERAL PUBLIC LICENSE This license allows you to make closed source commercial applications using uClibc Please consider sharing some of the money you make You do not need to give away all your source code just because you use uClibc and or run on Linux See the list of Frequently Asked Questions for details Sponsors Please visit our sponsors and thank them for their support They have provided money for equipment and bandwidth Next time you need help with a project consider these fine companies Penguru Consulting Custom development for embedded Linux systems and multimedia platforms opensource se Embedded open source consulting in Europe Codepoet Consulting Custom Linux

    Original URL path: http://www.uclibc.org/about.html (2015-03-26)
    Open archived version from archive

  • uClibc
    epoll h updates ldd host misc corrections Enjoy Iff you experience problems with this release then please file a bug 11 April 2012 uClibc 0 9 33 1 Released uClibc 0 9 33 1 was released today Grab the current 0 9 33 1 release tarball Refer to the ChangeLog 0 9 33 0 9 33 1 for the gory details or find and use other interresting stuff in the download area Changes include NPTL Fix static linking with signal related functions Add a microblaze specific sys user h stdio prevent retries on fclose fflush after write errors stdio Fix char signedness in load inttype fchmodat fix handling of flags libdl fix memleak for local scope of dlopened s needed libraries ldso fix fdpic support broken from prelink patch inotify rm watch Change second argument to int alpha trim crt code to fix build errors mmap64 always use unsigned 64bit offsets Enjoy 1 Feb 2012 uClibc 0 9 33 Released uClibc 0 9 33 was released today Grab the current 0 9 33 release tarball Refer to the ChangeLog 0 9 32 1 0 9 33 for an in depth description of changes Enjoy 30 Dec 2011 uClibc 0 9 33 rc1 Released Release candidate 1 for the upcoming 0 9 33 was released today Go to the downloads page and grab 0 9 33 rc1 release candidate See ChangeLog 0 9 32 1 0 9 33 rc1 for details Please test and report back to the mailing list 30 Dec 2011 uClibc 0 9 32 1 Released 0 9 32 1 is a bug fix release and a recommended update Head to the downloads page to pick up the 0 9 32 1 release The ChangeLog 0 9 32 0 9 32 1 has all the details Enjoy 08

    Original URL path: http://www.uclibc.org/news.html (2015-03-26)
    Open archived version from archive

  • uClibc
    development system depending on the options you selected Do I really need to build a uClibc toolchain Yes you really do need to build a toolchain to produce uClibc binaries We used to provide a toolchain wrapper but that has been removed due to numerous problems The uClibc developers have gone to a lot of trouble to produce the uClibc buildroot system which makes it easy to build your own uClibc toolchain and or an initial uClibc based system Feel free to take the gcc and binutils patches we provide and use them in your own toolchain build system If you choose to use your own toolchain build system you will need to use these patches since the upstream GNU binutils and gcc releases do not currently have full support for building a uClibc toolchain What happened to the old toolchain wrapper It is possible in some limited cases to re use an existing glibc toolchain and subvert it into building uClibc binaries by using gcc commands such as nostdlib and nostdinc In fact this used to be the recommended method for compiling programs with uClibc and we made this easy to do by providing a uClibc toolchain wrapper which attempted to automagically subvert an existing glibc toolchain This toolchain wrapper was removed from uClibc 0 9 22 and it will not be coming back This is because it proved impossible to completely subvert an existing toolchain in many cases and therefore proved to be a real maintainence burder As uClibc became more capable the many problems with re using an existing glibc toolchain led us to conclude that the only safe and sane way to build uClibc binaries was to use a uClibc toolchain Some discussion on the reasoning behind this decision can be found here http www uclibc org lists uclibc 2003 October 007315 html in the uClibc mailing list archives Is a pre compiled uClibc development system available If you want to be really lazy and start using uClibc right away without needing to compile your own toolchain or anything you can grab a pre compiled uClibc development system These are currently available for arm armeb i386 mips mipsel powerpc and sh4 These are bzip2 compressed ext2 filesystems containing all the development software you need to build your own uClibc applications including bash awk make gcc g autoconf automake ncurses zlib openssl openssh gdb strace busybox GNU coreutils GNU tar GNU grep etc Each of these uClibc development systems was created using buildroot These development systems should provide pretty much everything you need to get started building your own applications with uClibc Once you download one of these systems you can then boot into it loop mount it dd it to a spare drive and use a tool such as resize2fs to make it fill a partition Whatever works best for you The quickest way to get started using a root fs image using the i386 platform as an example is Download root fs i386 bz2 from uclibc org bunzip2 root fs i386 bz2 mkdir root fs su root mount o loop root fs i386 root fs chroot root fs bin su Type exit to end the chroot session and return to the host system What versions of linux gcc etc are supported While we never go out of our way to break support for older versions of tools reality is that slowly older versions fall by the wayside Certain versions of tools will be actively supported while support for older versions will require interested parties to submit a patch After all validation requires a lot of effort so it is unreasonable to ask the maintainers to validate older versions of tools when we ve already said we don t really care if the older versions work The current versions of things which are actively supported Linux 2 6 and newer The last two official GNU binutils releases The last few official stable GNU gcc releases We know that people like to run older versions of Linux such as the 2 2 and 2 4 series If things do not work for you on those series you will need to come up with a clean fix that can be merged into uClibc For threading libraries linuxthreads is planned to be maintained indefinitely so long as linux 2 4 support is active After that it will be the same as everything else left alone and hopefully left working The last two GNU binutils releases should work fine Workarounds for bugs in older versions are not considered The last official GCC point release is supported If you encounter a compile error using an older version then you re out of luck You ll need to workaround it yourself For the GNU toolchain releases only the latest point release is supported So if you encounter a bug in say GCC x y 7 but GCC x y 8 works fine then we will not address it Upgrading GCC across point releases is trivial Same goes for binutils I think I found a bug in uClibc What should I do A well written bug report should include small self contained example that demonstrates the problem behaviors Versions of the toolchain used uClibc gcc binutils etc Other relevant information that enables anyone else to reproduce the bug like the config you use For architecture specific bugs also mention the target triplet like armeb linux uclibcgnueabi For larger applications where it may prove difficult to provide an example application we recommend that you use a tool such as gdb strace ltrace and or valgrind to create a logfile showing the problem behavior If you find a problem with uClibc please submit a detailed bug report to the uClibc bug tracker If you are uncertain that it is a bug send the bug report containing the information listed above to the mailing list at uclibc uclibc org Please do not send private email to individual developers asking for private help unless you are planning

    Original URL path: http://www.uclibc.org/FAQ.html (2015-03-26)
    Open archived version from archive

  • uClibc
    compliant with the latest POSIX standard POSIX 1003 1 2008 Issue 7 POSIX 1003 1 2004 Issue 6 SystemV ABI SystemV Interface volume 1a SystemV Interface volume 1b SystemV Interface volume 2 These are documents related to the common ELF format ELF version 1 2 ELF 64 bit ELF Generic ABI Thread Local Storage TLS note also contains alpha ia64 s390 s390x sh x86 x86 64 These are architecture specific

    Original URL path: http://www.uclibc.org/specs.html (2015-03-26)
    Open archived version from archive

  • uClibc
    OpenEmbedded uCdot LinuxDevices Slashdot Freshmeat Linux Today Linux Weekly News Linux HOWTOs Download Source for the latest release can always be downloaded from http www uclibc org downloads You can also obtain Daily Snapshots of the latest development source tree for those wishing to follow uClibc development but cannot or do not wish to use Git Click here to browse the source tree Anonymous source access is available For those

    Original URL path: http://www.uclibc.org/download.html (2015-03-26)
    Open archived version from archive

  • uClibc
    copy of buildroot Unpack the tarball on your Linux system somewhere Edit the Makefile as needed if you wish to change anything run unset CC Then run unset CXX Some Linux systems i e Gentoo set variables such as CC in the system environment which really messes things up when cross compiling run make menuconfig Select the things you want to build If you only want a toolchain leave everything except the toolchain disabled save your buildroot configuration run make go eat a nice wholesome sandwich drink a pop call a friend play a video game and generally find something to do While you are waiting buildroot will download all the needed source code and then compile things up for you You should now have a shiny new toolchain and maybe even a shiny new uClibc based root filesystem or development system depending on the options you selected If you want to be really lazy and start using uClibc right away without needing to compile your own toolchain or anything you can grab a pre compiled uClibc development system These are currently available for arm armeb i386 mips mipsel powerpc and sh4 Note that the images mentioned above are old and ment for demonstration purposes only These are bzip2 compressed ext2 filesystems containing all the development software you need to build your own uClibc applications including bash awk make gcc g autoconf automake ncurses zlib openssl openssh gdb strace busybox GNU coreutils GNU tar GNU grep etc Each of these uClibc development systems was created using buildroot specifically buildroot 0 9 27 tar bz2 along with these sources These development systems should provide pretty much everything you need to get started building your own applications with uClibc Once you download one of these systems you can then boot into it

    Original URL path: http://www.uclibc.org/toolchains.html (2015-03-26)
    Open archived version from archive

  • uClibc
    use uClibc I d love to know about it and I d be happy to link to you I know of the following products and or projects that use uClibc listed in the order I happen to add them to the web page buildroot a configurable means for building your own busybox uClibc based system systems LEAF Bering uClibc the sucessor of the Linux Router Project supporting all sorts of

    Original URL path: http://www.uclibc.org/products.html (2015-03-26)
    Open archived version from archive