similar to: makeklcc.pl passes '' to ld if LDFLAGS empty among things

Stop makeklcc.pl from hardcoding paths of cc, ld and strip in the klcc script it generates. Using hardcoded paths is generally a bad idea. First, the whole idea of $PATH is that you don't need to hardcode paths. Second, klcc is a Perl script but my hardcoding the paths you make it less portable. Signed-off-by: Martin Michlmayr <tbm@cyrius.com> --- klibc-1.1.16/klcc/makeklcc.pl~

Commit-ID: 7752eb456addbd1973e9c6b609294ccef89a65a2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=7752eb456addbd1973e9c6b609294ccef89a65a2 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 20 Aug 2020 21:48:07 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 20 Aug 2020 21:50:09 +0100 [klibc] klcc: Treat CC, LD, STRIP

Though most people do have which installed somewhere. --- klibc/Makefile.orig 2005-04-08 18:34:56.827117248 +0200 +++ klibc/Makefile 2005-04-08 18:36:08.000297280 +0200 @@ -18,12 +18,12 @@ echo 'ARCH=$(ARCH)' >> $@ echo 'CROSS=$(CROSS)' >> $@ echo 'KCROSS=$(KCROSS)' >> $@ - echo "CC=$(shell bash -c 'type -p

Currently, in the entire klibc bash is only used to identify the path of the perl binary. It is doing so using the bash built-in 'type' function, which is POSIX compliant according to [0], but the option -c is not. By using `command -v` instead, we achieve the same result, in a POSIX compliant manor [1], potentially removing the unneeded bash dependency. 0

Commit-ID: 23273aa05bdc564eb8ff0565d9df9c3edfffaee9 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=23273aa05bdc564eb8ff0565d9df9c3edfffaee9 Author: Olliver Schinagl <oliver at schinagl.nl> AuthorDate: Sat, 25 Jul 2020 10:59:01 +0200 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 26 Jul 2020 00:16:13 +0100 klcc: Remove the need for bash

On Sat, 2020-07-25 at 10:59 +0200, Olliver Schinagl wrote: > Currently, in the entire klibc bash is only used to identify the path of > the perl binary. It is doing so using the bash built-in 'type' function, > which is POSIX compliant according to [0], but the option -c is not. > > By using `command -v` instead, we achieve the same result, in a POSIX > compliant manor

Ben Hutchings <ben at decadent.org.uk> wrote: > On Sat, 2020-07-25 at 10:59 +0200, Olliver Schinagl wrote: >> Currently, in the entire klibc bash is only used to identify the path of >> the perl binary. It is doing so using the bash built-in 'type' function, >> which is POSIX compliant according to [0], but the option -c is not. >> >> By using

Hi Currently I am trying to get device-mapper and dmraid ported to compile against klibc. So far there was no real issues, as the only thing they used was fscanf and feof not available presently in klibc (but easy to work around). Other than that there are really no way to easily check for installed klibc's other than trying to mangle the output of klcc (from adjusted configure.in): -----

Hi, I am getting this: ----- armv4-unknown-linux-gnu-ld -o tests/fcntl.shared -e main interp.o tests/fcntl.o -R libc.so /usr/lib/gcc-lib/armv4-unknown-linux-gnu/3.3.5/libgcc.a armv4-unknown-linux-gnu-ld: internal error: aborting at /space/var/tmp/portage/binutils-2.15.90.0.3-r4/work/binutils-2.15.90.0.3/ld/ldlang.c line 3835 in lang_place_orphans armv4-unknown-linux-gnu-ld: please report this

Hi, I hope this is the right list for initramfs questions. First I noticed: with initrd I can use real-root-device and pivot_root mechanisms. with initramfs only pivot_root works. My init (or linuxrc) scripts end like this: mount -t xfs -n -o ro /dev/mapper/root /new-root umount -n /sys || true umount -n /dev || true umount -n /proc || true cd /new-root pivot_root . initrd exec chroot .

working fine with glibc. thanks! Andreas -- ---------------------[ Ciphire Signature ]---------------------- From: aj@ciphirelabs.com signed email body (35 characters) Date: on 19 January 2005 at 12:48:14 GMT To: klibc@zytor.com ---------------------------------------------------------------- : The message above has been secured using Ciphire Mail. : Verify this signature and download your

Hi, please correct me if I'm wrong: - the kernel needs enough ram for the compressed initramfs and the same files decompressed, so it can decompress the files and boot the /init on the initramfs. - if the kernel does not have enough ram, it will kernel panic. my tests were done on a server with 256 mb ram and a 80MB compressed initrd. I removed some packages and now it fits and the

a bit unrelated, still I wonder: does syslinux contain an mbr? or does anyone know any app that contains an mbr and can install it, without overwriting the partition table? my experience is, that is wise to have an mbr and use the active flag to select the active partition (which might have a bootmanager installed). however every linux distribution I know installed the bootloader such as

Hi, So far with the latest changes the projects I am trying to port works fine, except for a mismatch on what is considered the ansi behaviour of islower() in ctype.h: ----- i = 220 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 220, TOUPPER (i) = 220 i = 221 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 221, TOUPPER (i) = 221 i = 222 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 222, TOUPPER

Hi, I'm using initramfs with pivot_root mechanism to mount my real root directory. I notived the gentoo halt.sh script tries to unmount everything on shutdown. That includes /initrd. The kernel seems to freeze immideatly. Do you have the same problems? Regards, Andreas CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAN_COMPILE=y

I've been working on a buildrelease.sh script to call hg2dist.sh, export debian/ from svn and run dpkg-source for me. When I ran dpkg-source I noticed that it gave warnings regarding the *.dpatch files being chmod 0755 is there any reason to maintain this within the repository or would 0644 suffice and remove these warnings from dpkg-source? Regards, Jeremy --

Hi, I've a samba server running samba-3.0.22 and a samba client running samba-2.2.3. The samba server houses the home directories of my users, registered on a W2k PDC. The home directories are mounted on the samba client and all members of the group GROUP have rwx-permissions to it. So my problem is that a group member cannot create symlinks on this mounted file system. Is there a way to get

I just also wanted to mention that I have the current released source tarballs downloaded and placed at http://people.debian.org/~jbouse/xen/ at this time. As the only way to get the source tarballs I've found is via bittorrent unless you want to give your email address I'll continue to keep the the current tarball located there. That is one thing that I noticed about Ralph's

Looking through the build files I'm wondering if we can't do some clean-up and remove extraneous kruft before we release. Like the config.dbs and the README.build that talks about the config.dbs. From looking through the build setup I don't see either file actually critically needed and looks like Ralph may have come to a similar conclusion by the comments added to the README.build

I've just been trying to catch up with the posts already so figured I'd just start another thread as it seemed I would address things from multiple emails. I really need to get my sieve filter script updated to move the list emails into the proper folder now I guess :) We can play with the revision of the packaging during testing. One idea would be to use 3.0.1-0.YYYYMMDD for