Re: Architecture usertags

2009-03-09 Thread Petr Salinger

so that maintainers could apply them to architecture-specific bugs when
necessary. The format, suggested by Steve Langasek, was to use the
porters mailinglist as the user, and the architecture name as the
usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as
tag).


Armel has already been using something similar:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org&tag=eabi

usertags would certainly be used a much more if there were a easy
way to set/search them on BTS web interface.


And GNU/kFreeBSD also have already something similar:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=kfreebsd;users=glibc-bsd-de...@lists.alioth.debian.org

Or better grouped

http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=kfreebsd;users=glibc-bsd-de...@lists.alioth.debian.org;pri0=pending:pending,forwarded,pending-fixed,fixed,done,absent;ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolved;pri1=pending%3dpending%2btag%3dwontfix,pending%3dpending%2btag%3dmoreinfo,pending%3dpending%2btag%3dpatch,pending%3dpending%2btag%3dconfirmed,pending%3dpending;ttl1=Will%20Not%20Fix,More%20information%20needed,Patch%20Available,Confirmed,Unclassified;ord1=2,3,4,1,0,5

Petr


--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: strange SIGSEV

2006-03-30 Thread Petr Salinger

Hi!


The following code seems to produce SIGSEV only on amd64 platforms (both on
GNU/Linux and on GNU/kFreeBSD).  Anyone has an idea what is the portability
problem here?


There is missing prototype for "char * getfoo();" in test.c.
When added, the first test also passes.

Well, next question would be why the second case passes
even without prototype ...

The difference between 1st and 2nd testcase is location of buf.
In the second case,  it is in main program,
it is mapped bellow 2GB mark - i.e. 0x5009e0.
In the first case, it is in shared library,
it is mapped above 2GB mark - i.e. 0x2acc1ca0.

Petr


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



amd64 glibc update for sarge

2006-03-16 Thread Petr Salinger
Hello,

> On glibc maintainers request, I have added glibc to the candidate for
> the next stable release on the wiki. [1]
> According to the diff between the packages, this update only concerns
> timezone data. There is no change in the glibc code.

When (and iff) will be glibc updated due to timezone, 
would be also possible to include fix specific to amd64 only (bug #314408) ?
Glibc with this fix is currently in sarge-unsupported archive for amd64.

Thanks for considering it.

Petr

--- libc/nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_unlock.S.jj 
+++ libc/nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_unlock.S
@@ -49,12 +49,12 @@ __pthread_rwlock_unlock:
 #endif
jnz 1f
 
-2: cmpq$0, WRITER(%rdi)
+2: cmpl$0, WRITER(%rdi)
jne 5f
declNR_READERS(%rdi)
jnz 6f
 
-5: movq$0, WRITER(%rdi)
+5: movl$0, WRITER(%rdi)
 
movq$1, %rsi
leaqWRITERS_WAKEUP(%rdi), %r10



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: 64 bit->48 bit pointer hacks...

2005-10-03 Thread Petr Salinger

> Is there some magic value I can write into "flag", that in
> combination with the understanding of how 64 bit pointers get
> truncated down to 48 bit virtual addresses that will allow me to

Technically, it is possible, but don't do it.
It is really terrible and non-portable hack.

amd64 is little endian, therefore:

class shortString {
   char smallString[7];
   char flag;
};

and the magic value for string is 64.
The string should be 0-terminated, therefore only 6 byte strings.

But again, don't do it.

Petr



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Trouble compiling transcode

2005-09-15 Thread Petr Salinger
Hi.

> gcc -shared .libs/import_ffmpeg.o -ldl -lz -lm -lpthread -lavcodec
> -L/usr/lib -Wl,-soname -Wl,import_ffmpeg.so -o .libs/import_ffmpeg.so
> /usr/bin/ld: /usr/lib/libavcodec.a(utils.o): relocation R_X86_64_32S 
> against `a local symbol' can not be used when making a shared object; 
> recompile with -fPIC


> I tried adding fPIC to the line:
> CFLAGS = -Wall -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -g -O2
> in Makefile, but no change.  

The key point is where to add -fPIC,
problem is in libavcodec.a, not the transcode.

Package libavcodec-dev contains two libraries, 
/usr/lib/libavcodec.a and  /usr/lib/libavcodec_pic.a

For creating shared library, you have to link with libavcodec_pic.

gcc -shared .libs/import_ffmpeg.o -ldl -lz -lm -lpthread -lavcodec_pic 
-L/usr/lib -Wl,-soname -Wl,import_ffmpeg.so -o .libs/import_ffmpeg.so

Regards

Petr



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: GetDP?

2005-08-19 Thread Petr Salinger

Hi.


Well, I can do my work like this, but still it is not really clear why:



1. the same library (eg. the same version) is not working in the normal
debian (read "default") setup?


You have to distinguish between using a library for running a program
and using a library (and its headers) for compiling a program.

For compiling you need also libgsl0-dev.

apt-get install build-essential g77 libgsl0-dev

After that I was able to compile  getdp-1.0.1.

$ ls  -l /usr/lib/libgsl.*

-rw-r--r--  1 root root 3600118 2005-04-11 01:17 /usr/lib/libgsl.a
lrwxrwxrwx  1 root root  15 2005-08-18 16:31 /usr/lib/libgsl.so -> 
libgsl.so.0.7.0
lrwxrwxrwx  1 root root  15 2005-08-18 16:31 /usr/lib/libgsl.so.0 -> 
libgsl.so.0.7.0
-rw-r--r--  1 root root 1738768 2005-04-11 01:17 /usr/lib/libgsl.so.0.7.0


Regards
Petr


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Pine

2005-06-09 Thread Petr Salinger
> Could anybody tell me how to install Pine on a AMD64 platform?

Pine license does not allow "modified binaries" to be distributed,
therefore:

apt-get build-dep pine
apt-get -b source pine


Regards 

Petr



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Tracking sarge (Failed to create initrd image)

2005-02-15 Thread Petr Salinger
> The linux-gate.so library is the 32bit emulation layer of the kernels
> 32bit support. I don't know why it has to show up like this but that
> is how it is.

This virtual ELF library is also in standard i386 2.6.x kernel.

Some information can be also found in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=209145


Fix for initrd-tools should be easy:

--- /usr/sbin/mkinitrd.std  2005-01-23 19:38:08.0 +0100
+++ /usr/sbin/mkinitrd  2005-02-15 18:46:16.0 +0100
@@ -821,7 +821,7 @@
else
x=$(
LD_LIBRARY_PATH=$INITRD_LD_LIBRARY_PATH \
-   ldd "$i"
+   ldd "$i" | grep -v linux-gate.so 
)
fi
err=$?

Petr



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]