On Wed, Apr 10, 2002 at 01:35:00PM +0200, Mattias Wadenstein wrote: > ld: 0711-317 ERROR: Undefined symbol: Base64Out<Base64StringOut>::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 -0000 1.11
+++ mimestream.hh 10 Apr 2002 12:33:30 -0000
@@ -83,7 +83,13 @@
Base64Out<Output>& 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 @@
Base64Out<Output>& Base64Out<Output>::write(const void* x, size_t n) {
return write(static_cast<const 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 Base64Out<Output>::code[] =
- //"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
- "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_";
template <class Output>
Base64Out<Output>& Base64Out<Output>::put(uint32 x) {
msg03329/pgp00000.pgp
Description: PGP signature
