The former setup64 doesn't complain, but I don't think this is a setup
problem. Rather, it's a difference between the generated ini files.
The old setup64.ini was only generated by genini, the new by upset.
For instance, here's the gcc entry generated by genini:
@ gcc
sdesc: "GNU Compiler Collection"
ldesc: "The GNU Compiler Collection includes front ends for C, C++,
Objective-C, Fortran, Java, Ada, and Go, as well as libraries for these
languages (libstdc++, libgcj,...)."
category: Devel
And here's the gcc entry as generated by upset:
@ gcc
sdesc: "GNU Compiler Collection"
ldesc: "The GNU Compiler Collection includes front ends for C, C++,
Objective-C, Fortran, Java, Ada, and Go, as well as libraries for these
languages (libstdc++, libgcj,...)."
category: Devel
version: 4.8.1-1
source: x86_64/release/gcc/gcc-4.8.1-1-src.tar.bz2 87070214 eb70273d8a2a555d995b0675980fcc1c
[prev]
version: 4.8.0-2
source: x86_64/release/gcc/gcc-4.8.0-2-src.tar.bz2 86977149 128658603c4daac97e62b4778c22a56d
So in one case the entry doesn't contain any package, in the other
case we have "source" entries. With the same input, I bet setup64
behaves the same as setup-x86_64.
[...time passes, testing...]
yes, when using the new setup.ini with the old setup64.exe, the effect
is the same.