multi-lib: oddness running the alienbob massconvert32 script
So I've recently installed the March 7th version of Slackware 64 Current on an extra partition. I've got a matching directory tree for Slackware 32 and the March 11th version of Alien Bob's multilib tools (the scripts, glibc and gcc). I upgraded all of the glibc & gcc packages without apparent problem.
Running the massconvert32.sh script to repack many 32-bit packages to a form compatible with the 64-bit system is where I may have run into a problem. Using the -n (dry run) option, I observed the following output: Code:
*** Starting the conversion process: I never saw a "continue: only meaningful in a `for', `while', or `until' loop" error message in shell script before. Is that a problem? |
Hello,
Quote:
The statement 'continue' at #221 is ignored because it is outside a for/while/until loop and should be replaced by a statement 'return'. -- SeB |
Quote:
|
Then it gets weird. I decided to run teh massconvert scritp anyway.
The packages that were claimed to not exist in the dry run (-n) phase suddenly existed. Oooooo kayyyyyy. Decided to not just blindly install the 32-bit compatibility packages, I picked one (elflibs (curiously enough, that was one of the packages that did not exist during the -n phase but did exist in the regular phase)) and ran "installpkg -test" on it. Conflict: some files were already there. Code:
# installpkg -warn aaa_elflibs-compat32-15.0-x86_64-5compat32.txz /usr/lib/libatomic.so.1.2.0 Odd though, wouldn't Patrick have placed the files in /usr/lib64 and not /usr/lib? p.s. Yes, I verified I did install the 64-bit version to begin with. |
Quote:
Please before you say any more, try to understand the reasons behind the "aaa_elflibs" package and why many of the libraries it contains also exist in other packages. |
All times are GMT -5. The time now is 12:23 AM. |