Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, Apr 10, 2002 at 08:54:58PM +0200, Mattias Wadenstein wrote: And that has the simple explanation of this line in the install-po part: @for file in ; do \ Which I commented out and now even make install works. :) Sorry to bother you with such a simple problem, but it is a bug. Thanks for reporting it! Both bash and ash treat this as do nothing and don't fail... I've fixed it here and also removed a few other bashisms in the Makefiles. Now it runs, and except for a few issues like segfaults when prompted with the wrong options and things like that, I now get: jigdo-file make-image: `woody-i386-1.raw.template' is not a template file For all values of templates and other options I have tried. That looks really bad! :-( I fear that for the moment, doing remote debugging would be too much work - two solutions: - Has anybody successfully compiled jigdo-file on AIX, and can provide (statically linked) binaries for Mattias? - If not, I'm going to update jigdo-port myself. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Tue, Apr 09, 2002 at 01:05:38PM +0200, Mattias Wadenstein wrote: [compiling jigdo-file] The version is: VisualAge C++ Professional / C for AIX Compiler, Version 5 And that is a new compiler, not a very old one. I know of a few sites that run much older ones. Sorry that jigdo is causing so much trouble. checking whether the C++ compiler is recent enough... no * Your compiler failed to recognize some advanced C++ * constructs. This means that it is probably too old. * In case compilation fails, try upgrading to a newer * compiler, e.g. GCC 2.95 or later. The C++ of the configure test is very hairy, jigdo doesn't actually use template specialization, so this warning might be bogus. I should probably change the configure test. It then procedes to fail to find db_create in -ldb[lots of versions] despite that being installed. --without-libdb gives a failure later on at: checking whether dgettext works... no * Make sure gettext is installed, or use * --disable-nls to switch off gettext support. configure: error: dgettext() call could not be linked. [snip] With g++ (and a bunch of hacking), it compiles but fails to link. It seems you have a linker problem both with the native compiler and g++. The libdb and gettext tests all call the linker. Once that is resolved, ./configure --without-gui (maybe also --disable-nls) should work. Also some interesting features turns up, like: checking size of unsigned long... 0 checking size of unsigned long long... 0 I've seen this myself on a Solaris machine with gcc - still need to get around to check what's causing it. I haven't had time to take a better look at it yet, or turn the software over to someone else around here. It is still painful, especially compared to jigdo-port which compiled cleanly and without problems. I'm very interested in getting it to compile cleanly on your machine. I guess it's not possible for me to get an account on your uni's machine so I can fix it myself? [jigdo mirror script] It isn't for the images, it is for having all the other files and directories looking exactly like the master site, a true mirror. Ah OK, I see. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
[EMAIL PROTECTED] (Richard Atterer) writes: On Tue, Apr 09, 2002 at 01:05:38PM +0200, Mattias Wadenstein wrote: [...] Also some interesting features turns up, like: checking size of unsigned long... 0 checking size of unsigned long long... 0 I've seen this myself on a Solaris machine with gcc - still need to get around to check what's causing it. IIRC that's again a linker issue, at least I had that problem on solaris. What does config.log look like ? Steffen msg03323/pgp0.pgp Description: PGP signature
Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, Apr 10, 2002 at 12:17:04PM +0200, Steffen Neumann wrote: checking size of unsigned long... 0 checking size of unsigned long long... 0 I've seen this myself on a Solaris machine with gcc - still need to get around to check what's causing it. IIRC that's again a linker issue, at least I had that problem on solaris. What does config.log look like ? Hm, I just tried again here, and it works flawlessly now - looks like they upgraded the compiler from gcc 2.95 to gcc 3.0.4. (From my experience, such weird problems are often caused by installing a GNU toolchain into a directory different from the one it was compiled for.) Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, Apr 10, 2002 at 01:35:00PM +0200, Mattias Wadenstein wrote:
ld: 0711-317 ERROR: Undefined symbol: Base64OutBase64StringOut::code
Hmm, /very/ interesting. I'm completely unable to tell whether my code
was valid C++. :) Anyway, try the attached patch.
I guess it's not possible for me to get an account on your uni's
machine so I can fix it myself?
Sorry, Rules from higher up. Outsiders not allowed.
I thought so - same over here.
Do you have a good documentation for the change in file format, so
that I could perhaps hack jigdo-port into working again?
Yes, check doc/TechDetails.txt in the jigdo source tarball, search for
obsolete. The change is simple; add support for reading the new
entry types 5 and 6.
Cheers,
Richard
--
__ _
|_) /| Richard Atterer | CS student at the Technische | GnuPG key:
| \/¯| http://atterer.net | Universität München, Germany | 0x888354F7
¯ '` ¯
Index: mimestream.hh
===
RCS file: /usr/local/cvsroot/jigdo/src/mimestream.hh,v
retrieving revision 1.11
diff -u -r1.11 mimestream.hh
--- mimestream.hh 16 Feb 2002 18:52:04 - 1.11
+++ mimestream.hh 10 Apr 2002 12:33:30 -
-83,7 +83,13
Base64OutOutput trailer(streamsize n);
private:
- static const char code[];
+ /* The first line (commented out) is the correct string for MIME
+ base64 encoding. We use the second instead because b64 strings
+ might be used as filenames for jigdo at one point. Additionally,
+ + or / looks weird in the .jigdo file. */
+ static const char* const code =
+//ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/;
+ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_;
void putBits();
int bits;
uint32 data;
-169,15 +175,6
Base64OutOutput Base64OutOutput::write(const void* x, size_t n) {
return write(static_castconst unsigned char*(x), n);
}
-
-/* The first line (commented out) is the correct string for MIME
- base64 encoding. We use the second instead because b64 strings
- might be used as filenames for jigdo at one point. Additionally,
- + or / looks weird in the .jigdo file. */
-template class Output
-const char Base64OutOutput::code[] =
- //ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/;
- ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_;
template class Output
Base64OutOutput Base64OutOutput::put(uint32 x) {
msg03329/pgp0.pgp
Description: PGP signature
Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, 10 Apr 2002, Richard Atterer wrote: On Wed, Apr 10, 2002 at 01:35:00PM +0200, Mattias Wadenstein wrote: ld: 0711-317 ERROR: Undefined symbol: Base64OutBase64StringOut::code Hmm, /very/ interesting. I'm completely unable to tell whether my code was valid C++. :) Anyway, try the attached patch. Thanks, now it compiles. And now for the next problem: /src/jigdo/jigdo-0.6.4/aix43# gmake install /bin/sh: 0403-057 Syntax error at line 1 : `;' is not expected. gmake: *** [install-po] Error 2 (Yes, that is all of the output. No, /bin/sh isn't bash.) Do you have a good documentation for the change in file format, so that I could perhaps hack jigdo-port into working again? Yes, check doc/TechDetails.txt in the jigdo source tarball, search for obsolete. The change is simple; add support for reading the new entry types 5 and 6. Ok, we'll see. I'm actually quite busy, despite my activity here. :) /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Wed, 10 Apr 2002, Mattias Wadenstein wrote: On Wed, 10 Apr 2002, Richard Atterer wrote: On Wed, Apr 10, 2002 at 01:35:00PM +0200, Mattias Wadenstein wrote: ld: 0711-317 ERROR: Undefined symbol: Base64OutBase64StringOut::code Hmm, /very/ interesting. I'm completely unable to tell whether my code was valid C++. :) Anyway, try the attached patch. Thanks, now it compiles. And now for the next problem: /src/jigdo/jigdo-0.6.4/aix43# gmake install /bin/sh: 0403-057 Syntax error at line 1 : `;' is not expected. gmake: *** [install-po] Error 2 (Yes, that is all of the output. No, /bin/sh isn't bash.) And that has the simple explanation of this line in the install-po part: @for file in ; do \ Which I commented out and now even make install works. :) Sorry to bother you with such a simple problem, but it is a bug. Now it runs, and except for a few issues like segfaults when prompted with the wrong options and things like that, I now get: jigdo-file make-image: `woody-i386-1.raw.template' is not a template file For all values of templates and other options I have tried. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Sun, Apr 07, 2002 at 01:04:56PM +0200, Mattias Wadenstein wrote: (Yes, jigdo-port is the only one that compiles on AIX for us. C++ isn't exactly portable. :/) Oh - but the file format has changed, and the latest jigdo files are no longer readable by jigdo-port! :-( I *really* want to avoid having to update two different programs whenever I make a change, so I have no plans to fix jigdo-port. [Standard rant: C++ *is* portable, and the standard has been out for 3 years - it's about time everybody caught up with it! Maybe gcc is boot-strappable on AIX... But I realize that would be quite a lot of work just to compile jigdo-file. :-( ] The important part is that the result looks exactly like the one on the master site so I can do an inexpensive rsync to get everything right. Should be possible. However, the template files include an md5sum of the images, which is checked by jigdo; if jigdo says that the file has been regenerated OK, it *is* OK and no extra rsync run is necessary. OTOH, it might make sense to fall back to rsync if not all of the parts in an image could be retrieved. I could add that to the script. Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Mon, 8 Apr 2002, Richard Atterer wrote: On Sun, Apr 07, 2002 at 01:04:56PM +0200, Mattias Wadenstein wrote: (Yes, jigdo-port is the only one that compiles on AIX for us. C++ isn't exactly portable. :/) Oh - but the file format has changed, and the latest jigdo files are no longer readable by jigdo-port! :-( I *really* want to avoid having to update two different programs whenever I make a change, so I have no plans to fix jigdo-port. [Standard rant: C++ *is* portable, and the standard has been out for 3 years - it's about time everybody caught up with it! Maybe gcc is boot-strappable on AIX... But I realize that would be quite a lot of work just to compile jigdo-file. :-( ] 3 years is a very short time. We have a fairly updated system, but 3 years is well below the time a system might be around without any updates other than security upgrades. The version is: VisualAge C++ Professional / C for AIX Compiler, Version 5 And that is a new compiler, not a very old one. I know of a few sites that run much older ones. Some configure output: checking whether the C++ compiler is recent enough... no * Your compiler failed to recognize some advanced C++ * constructs. This means that it is probably too old. * In case compilation fails, try upgrading to a newer * compiler, e.g. GCC 2.95 or later. It then procedes to fail to find db_create in -ldb[lots of versions] despite that being installed. --without-libdb gives a failure later on at: checking whether dgettext works... no * Make sure gettext is installed, or use * --disable-nls to switch off gettext support. configure: error: dgettext() call could not be linked. Also some interesting features turns up, like: checking size of unsigned long... 0 checking size of unsigned long long... 0 With g++ (and a bunch of hacking), it compiles but fails to link. I haven't had time to take a better look at it yet, or turn the software over to someone else around here. It is still painful, especially compared to jigdo-port which compiled cleanly and without problems. The important part is that the result looks exactly like the one on the master site so I can do an inexpensive rsync to get everything right. Should be possible. However, the template files include an md5sum of the images, which is checked by jigdo; if jigdo says that the file has been regenerated OK, it *is* OK and no extra rsync run is necessary. OTOH, it might make sense to fall back to rsync if not all of the parts in an image could be retrieved. I could add that to the script. It isn't for the images, it is for having all the other files and directories looking exactly like the master site, a true mirror. That is why I want the same directory structure, so that it will find the images with the correct size and not bother with them. If rsync believes it has to sync the images, it will put a great deal of load on both sides, even if the data is still the same. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.2_r6 jigdo files cdimage.d.o
On Sat, Apr 06, 2002 at 10:37:27PM +0200, Mattias Wadenstein wrote: Hmm.. This might be a very good idea if someone would write the jigdo-mirror script (or point me towards it if it is already done). It doesn't exist yet, but I'm willing to write it (later this week). Basically, what I'm thinking of is a script that can be run immediately after the rsyncs that update the FTP archive and the jigdo dir with all its contents. jigdo-mirror would walk through the jigdo dir, look for files like $jigdoDir/foo/bar/image.jigdo, and check whether any of those files is newer than the corresponding $imageDir/foo/bar/image.iso. If yes (the jigdo file was updated), it will (re)generate the image, using only the files on the local mirror. It will never try to download any missing files, instead it'll just abort and wait to be re-run after the next archive update. Hm, there'll also have to be an extra run over $imageDir to detect and delete any images whose jigdo files were removed. Is this what you want? For extra fun ftp.se.debian.org == ftp.gnome.org and the gnome desktop 2.0 release is currently scheduled for May 1st. :) LOL, hopefully your server won't go up in smoke... Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯ msg03214/pgp0.pgp Description: PGP signature
Re: 2.2_r6 jigdo files cdimage.d.o
On Sun, 7 Apr 2002, Richard Atterer wrote: On Sat, Apr 06, 2002 at 10:37:27PM +0200, Mattias Wadenstein wrote: Hmm.. This might be a very good idea if someone would write the jigdo-mirror script (or point me towards it if it is already done). It doesn't exist yet, but I'm willing to write it (later this week). Basically, what I'm thinking of is a script that can be run immediately after the rsyncs that update the FTP archive and the jigdo dir with all its contents. jigdo-mirror would walk through the jigdo dir, look for files like $jigdoDir/foo/bar/image.jigdo, and check whether any of those files is newer than the corresponding $imageDir/foo/bar/image.iso. If yes (the jigdo file was updated), it will (re)generate the image, using only the files on the local mirror. It will never try to download any missing files, instead it'll just abort and wait to be re-run after the next archive update. Hm, there'll also have to be an extra run over $imageDir to detect and delete any images whose jigdo files were removed. Is this what you want? If that would work, sure. If you have the time to write it. Otherwise a simple script that just makes all the images given a couple of directories ($jigdoDir, $imageDir and $archiveDir are the ones I can think of right now) would do fine. This should be trivial, but I haven't figured out how the arguments to jigdo-port works yet. (Yes, jigdo-port is the only one that compiles on AIX for us. C++ isn't exactly portable. :/) I'm currently updating the cd-image mirror by hand anyway. The important part is that the result looks exactly like the one on the master site so I can do an inexpensive rsync to get everything right. Hmm.. That brings another problem, the filesystem metadata has to look exactly right for that to work, otherwise rsync will assume that it has change and make the server calculate checksums. That could be solved with --size-only to rsync though, we just have to remember it. For extra fun ftp.se.debian.org == ftp.gnome.org and the gnome desktop 2.0 release is currently scheduled for May 1st. :) LOL, hopefully your server won't go up in smoke... We are working on finding a temporary home for it on borrowed hardware. That is also why I'm pointing out rsync-debcd.acc.umu.se now, the main ftp server might be very busy even with much bigger hardware than we currently have. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
